CVE-2026-8828: Chroma ChromaDB · Insecure Direct Object Reference
Affects Chroma ChromaDBSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ChromaChromaDB | Affected
| Fixed in– |
GitHubchromadbpkg:github/chromadbOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, restrict access to trusted users only and monitor for suspicious activity related to tenant data access. Avoid deploying vulnerable versions in production environments where tenant data isolation is critical.
Description
CVE-2026-8828 is a high-severity vulnerability in ChromaDB Rust project version 1.0.0 that allows any authenticated user to bypass authorization controls. This flaw enables users to read, write, update, or delete data in any tenant's collection regardless of their tenant membership. The vulnerability arises from a lack of authorization validation related to user-controlled keys.