CVE-2026-45831 — chromadb
Fix: chroma-core/chroma#7602CVE-2026-45831 is a CWE-863 vulnerability in chromadb. No vendor fix is recorded yet; mitigation options are listed below.
ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to
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 CVE-2026-45831.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
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
The SimpleRBACAuthorizationProvider authorization provider in versions 0.5.0 or later of the ChromaDB Python project evaluates whether a user holds a given permission but never checks which tenant, database, or collection that permission applies to allowing users to perform cross tenant actions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | chromadb | ≥ 0.5.0 | 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 CVE-2026-45831 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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
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.
is a post-authentication authorization flaw in ChromaDB’s SimpleRBAC provider — it does not grant unauthenticated access and does not enable code execution. RH AI products bundle a vulnerable chromadb version but do not run the Chroma Python server with SimpleRBAC as the default product architecture (AutoRAG uses…
To mitigate this issue, restrict network access to the ChromaDB instance to only trusted clients and services. Implement firewall rules to limit inbound connections to the ChromaDB port from authorized sources. If strict multi-tenant isolation is critical, consider deploying ChromaDB in a single-tenant configuration or exploring alternative authorization mechanisms if available, until a fix for the `SimpleRBACAuthorizationProvider` is deployed.Source: Red Hat security advisory for CVE-2026-45831 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-45831 in your dependencies?
Find it across PyPI, including transitive dependencies.