CVE-2026-86740: Improper Removal of Sensitive Information Before Storage or Transfer in grokability snipe-it
Affects grokability snipe-itSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium · fixed in 8.7.0 : update grokability snipe-it when convenient.
Data as of 10/25/2026, 04:40:14 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| grokabilitysnipe-it | Affected
| Fixed in
|
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Snipe-IT version 8.7.0. Users should upgrade to version 8.7.0 or later to ensure that file deletions are properly verified and that files are actually removed from storage. Until upgraded, administrators should manually verify file deletions at the filesystem level to ensure sensitive files are removed.
Description
Snipe-IT before 8.7.0 fails to check the return value of Storage::delete() in UploadedFilesController::destroy() and Api\\UploadedFilesController::destroy(), allowing deletion requests to report success while files remain on disk. Administrators performing attachment deletions receive success responses and see files hidden from listings, but the physical files persist on disk and remain accessible to anyone with filesystem or backup access.
Impact
Administrators receive false confirmation that files have been deleted, while the files remain physically present and accessible on disk or in backups. This could lead to unauthorized access to sensitive information that was believed to be deleted, potentially exposing confidential data.