CVE-2026-86739

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github.
generic

Snipe-IT before 8.7.0 Acceptance Finalization Without Stored Evidence | Advisories | VulnCheck

https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-acceptance-finalization-without-stored-evidence
github Patch Available

Acceptance Finalizes Without Stored Evidence Under Silent Storage Failure · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-h543-58f9-v6mj

Vendor Advisories for CVE-2026-86739(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:33 UTCGHSA enrichment
  3. 2026-09-18 17:30 UTCEG score recompute
  4. 2026-09-18 17:30 UTCGHSA enrichment
  5. 2026-09-18 14:23 UTCEG score recompute
  6. 2026-09-18 14:23 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 16:16 UTCGHSA enrichment
  9. 2026-09-16 18:11 UTCEG score recompute
  10. 2026-09-16 18:11 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 19:14 UTCEG score recompute
  14. 2026-09-15 19:14 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-14 21:08 UTCEG score recompute 3.40
  18. 2026-09-14 21:08 UTCGHSA enrichment
  19. 2026-09-14 21:01 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  20. 2026-09-13 01:16 UTCEG score recompute
  21. 2026-09-13 01:16 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-09 20:41 UTCEG score recompute
  25. 2026-09-09 20:41 UTCGHSA enrichment
Show 3 more
  1. 2026-09-09 14:27 UTCEG score recompute
  2. 2026-09-09 13:45 UTCEG score recompute
  3. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86739?
CVE-2026-86739 is a medium vulnerability published on September 9, 2026. 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…
When was CVE-2026-86739 disclosed?
CVE-2026-86739 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86739 actively exploited?
CVE-2026-86739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.3% of all scored CVEs.
What is the CVSS score of CVE-2026-86739?
CVE-2026-86739 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-86739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86739, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86739

Explore →

Is Your Infrastructure Affected by CVE-2026-86739?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.