CVE-2026-86739
Last modified
CVE-2026-86739 is a low-severity vulnerability rated 3.1/10 on the CVSS scale. Snipe-IT 8.6.3 and earlier do not check the return value of Storage::put() when writing the signature PNG and the generated acceptance PDF in Account\AcceptanceController::store(). On filesystem drivers that return false instead of throwing on a write failure (for example the local disk with restrictive permissions, S3 with expired credentials, or a storage backend that is out of quota), execution continues into $acceptance->accept(), which sets accepted_at and the signature_filename/eula_filename fields, creates the 'accepted' action-log entry, and dispatches completion notifications even though the evidence files were never stored.
Description
Snipe-IT 8.6.3 and earlier do not check the return value of Storage::put() when writing the signature PNG and the generated acceptance PDF in Account\AcceptanceController::store(). On filesystem drivers that return false instead of throwing on a write failure (for example the local disk with restrictive permissions, S3 with expired credentials, or a storage backend that is out of quota), execution continues into $acceptance->accept(), which sets accepted_at and the signature_filename/eula_filename fields, creates the 'accepted' action-log entry, and dispatches completion notifications even though the evidence files were never stored. The result is an acceptance record marked complete whose supporting evidence files do not exist, yielding a materially incomplete compliance artifact for EULA acknowledgement or equipment-receipt workflows. The condition is triggered when an authenticated user completes an acceptance while the storage backend is silently failing writes; an attacker cannot directly force the storage backend into that state. Fixed in Snipe-IT 8.7.0.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| grokability | snipe-it | < 8.7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-86739?
How severe is CVE-2026-86739?
How do I fix CVE-2026-86739?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-86733Snipe-IT before 8.7.0 streams the SQL entry from an uploaded…7.2
- CVE-2026-86734Snipe-IT before 8.7.1 fails to validate the length of the no…6.5
- CVE-2026-86735snipe-it versions before 8.7.0 contain a server-side request…5
- CVE-2026-86736snipe-it before 8.7.0 contains an incorrect calculation vuln…4.3
- CVE-2026-86737snipe-it versions before 8.7.0 fail to enforce asset view au…4.3
- CVE-2026-86738Snipe-IT versions before 8.7.0 contain a CSS injection vulne…8.7
- CVE-2026-86740Snipe-IT before 8.7.0 fails to check the return value of Sto…3.8
- CVE-2026-86741Snipe-IT versions before 8.7.0 fail to sanitize the category…8.5
- CVE-2026-86742Snipe-IT through 8.6.3 does not neutralize formula elements …6.5
- CVE-2026-86743Snipe-IT versions before 8.7.0 fail to properly scope asset …5
- CVE-2026-86744Snipe-IT 8.6.3 and earlier (and develop pre-release commits …2.2
- CVE-2026-86745Snipe-IT is an IT asset management application. In Snipe-IT …6.5
Are you affected by CVE-2026-86739?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
