CVE-2026-86766

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
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: Elevated riskExposed: 0

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

Snipe-IT versions up to and including 8.6.3 contain a race condition (TOCTOU) in the consumable checkout API endpoint (POST /api/v1/consumables/{consumable_id}/checkout). The requested quantity is validated against the number of remaining units before the database transaction begins, and the transaction then creates the checkout records without locking the consumable row or re-checking availability. An authenticated user with permission to check out consumables can submit concurrent checkout requests for the same consumable so that both requests pass the availability check and succeed, over-allocating stock and driving the remaining inventory negative (e.g., a consumable with 1 remaining unit ends at -1 after two concurrent 1-unit checkouts). The issue is fixed in 8.7.0, which re-fetches the parent row under lockForUpdate inside the transaction and re-validates availability.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
45(Track)
EG Risk 45/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

Snipe-IT 8.6.3 Race Condition via Consumable Checkout | Advisories | VulnCheck

https://www.vulncheck.com/advisories/snipe-it-8.6.3-race-condition-via-consumable-checkout
github_commit Patch Available

commit f71806b1e0ef (grokability/snipe-it)

Patch available: grokability/snipe-it v8.7.0 (contains commit f71806b1e0ef)

https://github.com/grokability/snipe-it/commit/f71806b1e0efbd3bc2b6be61994ad2a5d5d6c206
github Patch Available🟡 PoC Available

Consumable Inventory Over-allocation Through Concurrent Checkout Requests · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-x4g2-87xc-m5jm

Vendor Advisories for CVE-2026-86766(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 20× in last 7d / 35× 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-20 23:36 UTCEG score recompute
  2. 2026-09-20 23:36 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-19 22:59 UTCEG score recompute
  5. 2026-09-19 22:59 UTCGHSA enrichment
  6. 2026-09-18 22:22 UTCEG score recompute
  7. 2026-09-18 22:22 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 21:46 UTCEG score recompute
  10. 2026-09-17 21:46 UTCGHSA enrichment
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-16 21:09 UTCEG score recompute
  13. 2026-09-16 21:09 UTCGHSA enrichment
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 00:22 UTCEG score recompute
  17. 2026-09-16 00:21 UTCGHSA enrichment
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 23:43 UTCGHSA enrichment
  21. 2026-09-13 23:06 UTCEG score recompute
  22. 2026-09-13 23:06 UTCGHSA enrichment
  23. 2026-09-12 22:29 UTCEG score recompute
  24. 2026-09-12 22:29 UTCGHSA enrichment
  25. 2026-09-11 21:53 UTCEG score recompute
Show 10 more
  1. 2026-09-11 21:53 UTCGHSA enrichment
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-10 21:16 UTCGHSA enrichment
  5. 2026-09-09 20:40 UTCEG score recompute
  6. 2026-09-09 20:40 UTCGHSA enrichment
  7. 2026-09-09 15:28 UTCEG score recompute
  8. 2026-09-09 14:20 UTCEG score recompute
  9. 2026-09-09 13:45 UTCEG score recompute
  10. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86766?
CVE-2026-86766 is a medium vulnerability published on September 9, 2026. Snipe-IT versions up to and including 8.6.3 contain a race condition (TOCTOU) in the consumable checkout API endpoint (POST /api/v1/consumables/{consumable_id}/checkout). The requested quantity is validated against the number of remaining units before the database transaction begins, and the…
When was CVE-2026-86766 disclosed?
CVE-2026-86766 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86766 actively exploited?
CVE-2026-86766 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 86.0% of all scored CVEs.
What is the CVSS score of CVE-2026-86766?
CVE-2026-86766 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-86766?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86766, 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-86766

Explore →

Is Your Infrastructure Affected by CVE-2026-86766?

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

Start Free Scan →Browse All CVEs