CVE-2026-86739
CVE-2026-86739 is a low-severity vulnerability in Snipeitapp Snipe-it with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-252.
Key facts
- Severity: Low (CVSS 3.x base score 3.1)
- CVSS v4: 2.3
- EPSS exploit prediction: 0% (27th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-252
- Affected product: Snipeitapp Snipe-it
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-86739?
- 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.
- How severe is CVE-2026-86739?
- CVE-2026-86739 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
- Is CVE-2026-86739 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-86739?
- CVE-2026-86739 affects Snipeitapp Snipe-it. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-86739?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-86739 published?
- CVE-2026-86739 was published on 2026-09-09 and last updated on 2026-09-18.
References
- https://github.com/grokability/snipe-it/security/advisories/GHSA-h543-58f9-v6mj
- https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-acceptance-finalization-without-stored-evidence
Affected products (1)
- cpe:2.3:a:snipeitapp:snipe-it:*:*:*:*:*:*:*:*
More vulnerabilities in Snipeitapp Snipe-it
- CVE-2025-63601 — Critical (CVSS 9.9): Snipe-IT before version 8.3.3 contains a remote code execution vulnerability that allows an authenticated attacker to…
- CVE-2026-37709 — Critical (CVSS 9.8): Insecure Permissions vulnerability in grokability snipe-it v.8.4.0 and before and fixed after 2026-03-10 commit…
- CVE-2026-85617 — High (CVSS 8.8): snipe-it versions before 8.6.3 contain an authorization bypass vulnerability in the bulk delete functionality that…
- CVE-2026-55643 — High (CVSS 8.8): Snipe-IT is an IT asset/license management system. Prior to 8.6.3, a company-scoped user in FMCS floater mode can…
- CVE-2026-55483 — High (CVSS 8.8): Snipe-IT is an IT asset/license management system. Prior to 8.6.0, an authenticated user with users.create permission…
- CVE-2026-44832 — High (CVSS 8.8): Snipe-IT is an IT asset/license management system. Prior to 8.4.1, aAn authenticated user with only users.edit…
All CVEs affecting Snipeitapp Snipe-it →
Other CWE-252 vulnerabilities
- CVE-2025-66565 — Critical (CVSS 9.8): Fiber Utils is a collection of common functions created for Fiber. In versions 2.0.0-rc.3 and below, when the system's…
- CVE-2023-52687 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: crypto: safexcel - Add error handling for…
- CVE-2021-38171 — Critical (CVSS 9.8): adts_decode_extradata in libavformat/adtsenc.c in FFmpeg 4.4 does not check the init_get_bits return value, which is a…
- CVE-2021-26955 — Critical (CVSS 9.8): An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because…
- CVE-1999-0199 — Critical (CVSS 9.8): manual/search.texi in the GNU C Library (aka glibc) before 2.2 lacks a statement about the unspecified tdelete return…
- CVE-2019-15900 — Critical (CVSS 9.8): An issue was discovered in slicer69 doas before 6.2 on certain platforms other than OpenBSD. On platforms without…