Servers and applications
CVE-2026-86740
Attachment Deletion Reports Success While File Remains on Disk
- Severity
- Medium 5.1
- Published
- 24 Aug 2026
- Last changed
- 14 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 8.7.0
- Exploit chance
- 0.3% in the next 30 daysHigher than 22% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs an administrator account · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/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-4c4h-cpgf-h4qr
- Sources
- NVD, Project advisories (GitHub)
Description
UploadedFilesController::destroy() (web) and Api\UploadedFilesController::destroy() (API) both called Storage::delete() without checking the return value, then created an upload deleted action-log entry and returned a success response unconditionally. HasUploads::uploads() excludes files whose filename matches an upload deleted log for the same object, so a silently-failed physical delete produced a state where:
- The bytes remain on disk (nobody removed them).
- An action log states the file has been deleted.
- The admin sees a "success" response to the delete request.
- The attachment no longer appears in the normal UI listing (HasUploads hides it).
An administrator asked to purge a sensitive attachment (a signed contract that needs to disappear, an old signature block, a document the data subject requested erased) is told the deletion succeeded while the bytes are still on disk and are still accessible by anyone with direct filesystem or backup access.
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-86740
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-86740
- GitHub Advisory Database https://github.com/advisories/GHSA-4c4h-cpgf-h4qr
- github.com https://github.com/grokability/snipe-it/security/advisories/GHSA-4c4h-cpgf-h4qr