Servers and applications
CVE-2026-86749
Failed Image Write Destroys Existing Image and Leaves Model Pointing at Phantom File
- Severity
- High 7.0
- Published
- 24 Aug 2026
- Last changed
- 19 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 8.7.0
- Exploit chance
- 0.3% in the next 30 daysHigher than 27% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · Needs someone to view a page or file
- Attacker can
- Change data · Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-v37p-hr9x-5w85
- Sources
- NVD, Project advisories (GitHub)
Description
ImageUploadRequest::handleImages() ignored the return value of every Storage::disk('public')->put(...) call, then unconditionally deleted the previous image and reassigned the model's image reference to the new filename. When the storage write silently failed (Laravel's default disk mode does not throw on failure), the flow still ran the delete and the model reassignment, so the old image was destroyed and the model row ended up referencing a file that never landed on disk. The same shape existed in deleteExistingImage(), where a failed delete still nulled the model's image reference, orphaning the file on disk.
Not attacker-controlled directly. Any legitimate user submitting an image upload could trigger the bug when the storage backend transiently failed (S3 network hiccup, permission blip on the local disk, quota exhaustion). The bug's severity is data-loss under that legitimate use case, not a privilege escalation.
Affected software
| Software | Affected versions |
|---|---|
Snipe-ITServers and applications · cpe:a:snipeitapp:snipe-it |
|
Snipe-ITServers and applications · github:grokability/snipe-it |
|
About Snipe-IT
A free open source IT asset/license management system
- Docker Hub pulls
- 29,869,543Docker Hub, 15 Nov 2026
- GitHub stars
- 15,189GitHub, 15 Nov 2026
- Forks
- 4,068GitHub, 15 Nov 2026
- Latest release
- v8.8.3GitHub, 15 Nov 2026
- Released
- 22 Oct 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 12 Nov 2013GitHub
Source code Website Docker image
Vulnerabilities in Snipe-IT
- In our list
- 142
- Published in the last 12 months
- 103
- Critical, last 12 months
- 3
- High, last 12 months
- 35
- Known exploited
- 0
- GHSA-48v6-cj87-4phgOIDC API bearer resolver skips exact-username match, allowing collation-folded username collision ATOHigh 8.1 17 Nov 2026
- CVE-2026-116201Snipe-IT before 8.5.0 SAML Assertion Replay via Race ConditionHigh 8.7 25 Oct 2026
- CVE-2026-116200Snipe-IT before 8.6.3 LDAP StartTLS Downgrade via connectToLdap()High 8.2 25 Oct 2026
- CVE-2026-116199Snipe-IT before 8.6.3 Authentication Bypass via Google SSO CallbackCritical 9.2 25 Oct 2026
- CVE-2026-116198Snipe-IT before 8.7.0 Missing Encryption via Api AssetsController storeMedium 5.3 25 Oct 2026
- CVE-2026-114064Snipe-IT before 8.7.0 SSRF Port Scanning via Webhook Testing EndpointMedium 5.1 21 Oct 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-86749
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-86749
- GitHub Advisory Database https://github.com/advisories/GHSA-v37p-hr9x-5w85
- github.com https://github.com/grokability/snipe-it/security/advisories/GHSA-v37p-hr9x-5w85