ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collectionGHSA-2wm9-hf6c-p5cr
HIGHFix: chroma-core/chroma#7602GHSA-2wm9-hf6c-p5cr is a high-severity (CVSS 8.8) CWE-639 vulnerability in chromadb. No vendor fix is recorded yet; mitigation options are listed below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2wm9-hf6c-p5cr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-2wm9-hf6c-p5cr by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
chromadbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection regardless of which tenant they belong to.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | chromadb | ≥ 0.4.17 | No fix |
Affected Products
chromadbtrychromaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chromadb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of chromadb has shipped for GHSA-2wm9-hf6c-p5cr yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This flaw is Post-authentication IDOR: ChromaDB resolves collections by UUID without tenant/database filtering, allowing any authenticated user who knows a collection UUID to access any tenant’s data. High severity for confidentiality and integrity; not Critical because authentication is required and there is no code…
To reduce the attack surface, restrict network access to ChromaDB instances to only trusted clients and internal networks. Implement network segmentation and firewall rules to limit exposure of the ChromaDB service. This operational control helps prevent unauthorized access to the service, although it does not address the internal authorization bypass for already authenticated users.Source: Red Hat security advisory for GHSA-2wm9-hf6c-p5cr (CC BY 4.0)
Frequently Asked Questions
Is GHSA-2wm9-hf6c-p5cr in your dependencies?
Find it across PyPI, including transitive dependencies.