CVE-2026-92782

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

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

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

Chroma through 1.5.9 fails to validate tenant and database segments when resolving collections, allowing authenticated attackers to access collections from other tenants by knowing the collection identifier. Attackers can read, modify, and update records in foreign collections by issuing requests under their own tenant path, bypassing authorization checks.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

Chroma through 1.5.9 Authorization Bypass via Collection Identifier | Advisories | VulnCheck

https://www.vulncheck.com/advisories/chroma-through-1.5.9-authorization-bypass-via-collection-identifier
generic

chroma/rust/frontend/src/get_collection_with_segments_provider.rs at 1.5.9 · chroma-core/chroma · GitHub

https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/get_collection_with_segments_provider.rs#L143-L160
generic

chroma/rust/frontend/src/server.rs at 1.5.9 · chroma-core/chroma · GitHub

https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/server.rs#L469-L487
generic

GitHub - chroma-core/chroma: Search infrastructure for AI · GitHub

https://github.com/chroma-core/chroma
generic

Cross-tenant/cross-database collection read, write, and metadata tampering via UUID-only collection resolution (tenant/database URL path ignored) · Issue #7462 · chroma-core/chroma · GitHub

https://github.com/chroma-core/chroma/issues/7462

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92782?
CVE-2026-92782 is a high vulnerability published on September 16, 2026. Chroma through 1.5.9 fails to validate tenant and database segments when resolving collections, allowing authenticated attackers to access collections from other tenants by knowing the collection identifier. Attackers can read, modify, and update records in foreign collections by issuing requests…
When was CVE-2026-92782 disclosed?
CVE-2026-92782 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92782 actively exploited?
CVE-2026-92782 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 63.8% of all scored CVEs.
What is the CVSS score of CVE-2026-92782?
CVE-2026-92782 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-92782?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92782, 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-92782

Explore →

Is Your Infrastructure Affected by CVE-2026-92782?

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

Book a Demo →Browse All CVEs