CVE-2026-86750

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

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

Snipe-IT versions <= 8.6.3 (fixed in 8.7.0) do not validate company assignment authorization before persisting user records via the REST API. In Api\UsersController::store() and ::update(), the user record is filled from the request and saved before the requested company_id / company_ids[] values are filtered against the actor's permitted companies (Company::getIdsForCurrentUser()). On installs using Full Multiple Companies Support (FMCS), a non-superuser holding users.create (or users.edit on a target user) can submit company identifiers for companies outside their scope — including a mix of permitted and foreign ids — causing the account row to be committed to the database before authorization is checked. Where null_company_is_floater=1 is set, the post-hoc filter leaves an empty company pivot and the account is persisted as a "floater" with cross-company visibility, allowing creation or relocation of user accounts across tenant boundaries.

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

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (2)

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

snipe-it before 8.7.0 Authorization Bypass via API User Create/Update | Advisories | VulnCheck

https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-authorization-bypass-via-api-user-create-update
github Patch Available

API User Create/Update Persists Cross-Tenant Company Assignment Before Authorization · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-c929-qxg6-r3mc

Vendor Advisories for CVE-2026-86750(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 24× in last 7d / 63× 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 04:14 UTCGHSA enrichment
  2. 2026-09-24 15:15 UTCEG score recompute
  3. 2026-09-24 15:15 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 02:03 UTCGHSA enrichment
  6. 2026-09-23 13:05 UTCGHSA enrichment
  7. 2026-09-23 00:06 UTCEG score recompute
  8. 2026-09-23 00:06 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-22 11:06 UTCGHSA enrichment
  11. 2026-09-21 22:08 UTCEG score recompute
  12. 2026-09-21 22:08 UTCGHSA enrichment
  13. 2026-09-21 21:09 UTCEPSS rescore
  14. 2026-09-21 09:08 UTCEG score recompute
  15. 2026-09-21 09:08 UTCGHSA enrichment
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-20 20:09 UTCGHSA enrichment
  18. 2026-09-20 07:10 UTCGHSA enrichment
  19. 2026-09-19 18:11 UTCEG score recompute
  20. 2026-09-19 18:11 UTCGHSA enrichment
  21. 2026-09-19 05:12 UTCEG score recompute
  22. 2026-09-19 05:12 UTCGHSA enrichment
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-18 16:13 UTCGHSA enrichment
  25. 2026-09-18 02:34 UTCEG score recompute
Show 38 more
  1. 2026-09-18 02:34 UTCGHSA enrichment
  2. 2026-09-17 19:32 UTCEPSS rescore
  3. 2026-09-17 13:35 UTCGHSA enrichment
  4. 2026-09-17 00:36 UTCEG score recompute
  5. 2026-09-17 00:36 UTCGHSA enrichment
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 11:36 UTCEG score recompute
  8. 2026-09-16 11:36 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 22:33 UTCGHSA enrichment
  11. 2026-09-15 09:34 UTCEG score recompute
  12. 2026-09-15 09:34 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-14 20:35 UTCGHSA enrichment
  16. 2026-09-14 14:31 UTCEG score recompute
  17. 2026-09-14 14:31 UTCGHSA enrichment
  18. 2026-09-14 13:36 UTCEG score recompute
  19. 2026-09-14 13:36 UTCGHSA enrichment
  20. 2026-09-14 04:36 UTCEG score recompute
  21. 2026-09-14 04:36 UTCGHSA enrichment
  22. 2026-09-13 15:37 UTCGHSA enrichment
  23. 2026-09-13 02:35 UTCEG score recompute
  24. 2026-09-13 02:35 UTCGHSA enrichment
  25. 2026-09-12 13:36 UTCGHSA enrichment
  26. 2026-09-12 00:37 UTCEG score recompute
  27. 2026-09-12 00:37 UTCGHSA enrichment
  28. 2026-09-11 14:53 UTCEPSS rescore
  29. 2026-09-11 14:53 UTCEPSS rescore
  30. 2026-09-11 11:38 UTCEG score recompute
  31. 2026-09-11 11:38 UTCGHSA enrichment
  32. 2026-09-10 22:39 UTCGHSA enrichment
  33. 2026-09-10 09:40 UTCGHSA enrichment
  34. 2026-09-09 20:41 UTCEG score recompute
  35. 2026-09-09 20:41 UTCGHSA enrichment
  36. 2026-09-09 14:26 UTCEG score recompute
  37. 2026-09-09 13:45 UTCEG score recompute
  38. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86750?
CVE-2026-86750 is a high vulnerability published on September 9, 2026. Snipe-IT versions <= 8.6.3 (fixed in 8.7.0) do not validate company assignment authorization before persisting user records via the REST API. In Api\UsersController::store() and ::update(), the user record is filled from the request and saved before the requested companyid / companyids[] values are…
When was CVE-2026-86750 disclosed?
CVE-2026-86750 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86750 actively exploited?
CVE-2026-86750 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 77.2% of all scored CVEs.
What is the CVSS score of CVE-2026-86750?
CVE-2026-86750 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-86750?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86750, 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-86750

Explore →

Is Your Infrastructure Affected by CVE-2026-86750?

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