CVE-2026-86744

LOWPre-NVD 2.22.2—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
2.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.2Exploit: 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 (and develop pre-release commits prior to the fix) contain a race condition in the asset checkout paths. Api\AssetsController::checkout() and Assets\AssetCheckoutController::store() call Asset::availableForCheckout() outside the mutation path and then invoke Asset::checkOut() without taking a row lock or re-checking availability, so two concurrent checkout requests for the same available asset can both observe it as available and both commit. This produces duplicate checkout-history rows, a doubled checkout_counter, and two CheckoutableCheckedOut events for a single-assignment asset, corrupting the audit trail and utilization/reconciliation reporting; the asset's final assigned_to remains singular, so the visible assignment stays intact. Exploitation requires an authenticated session holding the assets.checkout permission (or superuser) and precise concurrent timing. Fixed in 8.7.0.

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

Published

September 9, 2026

Last Modified

September 18, 2026

References (3)

Vendor Advisories for CVE-2026-86744(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 15× in last 7d / 24× 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 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 18:33 UTCEG score recompute
  4. 2026-09-18 18:33 UTCGHSA enrichment
  5. 2026-09-18 17:30 UTCEG score recompute
  6. 2026-09-18 17:30 UTCGHSA enrichment
  7. 2026-09-18 01:33 UTCEG score recompute
  8. 2026-09-18 01:33 UTCGHSA enrichment
  9. 2026-09-17 19:32 UTCEPSS rescore
  10. 2026-09-16 14:09 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 20:41 UTCEG score recompute
  15. 2026-09-14 20:41 UTCGHSA enrichment
  16. 2026-09-13 01:33 UTCEG score recompute
  17. 2026-09-13 01:33 UTCGHSA enrichment
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-09 20:41 UTCEG score recompute
  21. 2026-09-09 20:41 UTCGHSA enrichment
  22. 2026-09-09 14:27 UTCEG score recompute
  23. 2026-09-09 13:45 UTCEG score recompute
  24. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86744?
CVE-2026-86744 is a low vulnerability published on September 9, 2026. Snipe-IT 8.6.3 and earlier (and develop pre-release commits prior to the fix) contain a race condition in the asset checkout paths. Api\AssetsController::checkout() and Assets\AssetCheckoutController::store() call Asset::availableForCheckout() outside the mutation path and then invoke…
When was CVE-2026-86744 disclosed?
CVE-2026-86744 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-86744 actively exploited?
CVE-2026-86744 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 88.2% of all scored CVEs.
What is the CVSS score of CVE-2026-86744?
CVE-2026-86744 has a CVSS v3 base score of 2.2 (NVD).
How do I remediate CVE-2026-86744?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86744, 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-86744

Explore →

Is Your Infrastructure Affected by CVE-2026-86744?

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

Start Free Scan →Browse All CVEs