CVE-2026-86773

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: Elevated riskExposed: 0

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

Snipe-IT through version 8.6.3 fails to perform object-level authorization in the updateLicense, updateConsumable, updateAccessory, and updateModel endpoints and in the storeModel endpoint for Predefined Kits. The existing check authorizes only the parent Predefined Kit (update on PredefinedKit) and not the child object being attached. As a result, an authenticated user holding only the kits.edit permission can attach a License, Consumable, Accessory, or Asset Model that they are otherwise denied (HTTP 403) from reading directly to a Predefined Kit, and the kit relation index then discloses the attached object's name back to that low-privilege user. This is the update-path and storeModel counterpart to CVE-2026-55478, which fixed only the storeLicense, storeConsumable, and storeAccessory methods in 8.6.2. Note that updateModel was code-vulnerable in 8.6.3 but not reachable in practice because a route-name typo bound the route to a nonexistent controller method, causing HTTP 500 responses. The issue is fixed in Snipe-IT 8.7.0.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
40(Track)
EG Risk 40/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
Severity54% × 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 (2)

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

Snipe-IT 8.6.3 Broken Access Control via Kit Update Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/snipe-it-8.6.3-broken-access-control-via-kit-update-endpoints
github Patch Available🟡 PoC Available

Broken Access Control in Predefined Kit Update / storeModel Endpoints · Advisory · grokability/snipe-it · GitHub

Affected: v8.6.2 by the

https://github.com/grokability/snipe-it/security/advisories/GHSA-4j5f-mm59-hf9w

Vendor Advisories for CVE-2026-86773(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 / 48× 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-25 00:24 UTCEG score recompute
  2. 2026-09-25 00:24 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 00:00 UTCEG score recompute
  5. 2026-09-24 00:00 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-22 23:35 UTCEG score recompute
  8. 2026-09-22 23:35 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-21 23:08 UTCEG score recompute
  11. 2026-09-21 23:08 UTCGHSA enrichment
  12. 2026-09-21 21:09 UTCEPSS rescore
  13. 2026-09-20 22:45 UTCEG score recompute
  14. 2026-09-20 22:45 UTCGHSA enrichment
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-19 22:20 UTCEG score recompute
  17. 2026-09-19 22:20 UTCGHSA enrichment
  18. 2026-09-18 21:56 UTCEG score recompute
  19. 2026-09-18 21:56 UTCGHSA enrichment
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-17 21:32 UTCEG score recompute
  22. 2026-09-17 21:32 UTCGHSA enrichment
  23. 2026-09-17 19:32 UTCEPSS rescore
  24. 2026-09-16 21:08 UTCEG score recompute
  25. 2026-09-16 21:08 UTCGHSA enrichment
Show 23 more
  1. 2026-09-16 14:09 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 23:19 UTCEG score recompute
  4. 2026-09-15 23:18 UTCGHSA enrichment
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-14 22:40 UTCGHSA enrichment
  8. 2026-09-13 22:16 UTCEG score recompute
  9. 2026-09-13 22:16 UTCGHSA enrichment
  10. 2026-09-12 21:52 UTCEG score recompute
  11. 2026-09-12 21:52 UTCGHSA enrichment
  12. 2026-09-11 21:28 UTCEG score recompute
  13. 2026-09-11 21:28 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 21:04 UTCGHSA enrichment
  17. 2026-09-09 20:40 UTCEG score recompute
  18. 2026-09-09 20:39 UTCGHSA enrichment
  19. 2026-09-09 15:28 UTCEG score recompute
  20. 2026-09-09 14:45 UTCEG score recompute
  21. 2026-09-09 14:26 UTCEG score recompute
  22. 2026-09-09 13:45 UTCEG score recompute
  23. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86773?
CVE-2026-86773 is a medium vulnerability published on September 9, 2026. Snipe-IT through version 8.6.3 fails to perform object-level authorization in the updateLicense, updateConsumable, updateAccessory, and updateModel endpoints and in the storeModel endpoint for Predefined Kits. The existing check authorizes only the parent Predefined Kit (update on PredefinedKit)…
When was CVE-2026-86773 disclosed?
CVE-2026-86773 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-86773 actively exploited?
CVE-2026-86773 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 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-86773?
CVE-2026-86773 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-86773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86773, 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-86773

Explore →

Is Your Infrastructure Affected by CVE-2026-86773?

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

Book a Demo →Browse All CVEs