chromadb Known Vulnerabilities & Fixes
chromadb has 2 known security vulnerabilities in PyPI (Python). Review the table below for affected and fixed versions. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Is chromadb in your project?
Check if you're affected by these 2 vulnerabilities.
Security Summary
- 2 affected version ranges have been identified across these 2 advisories.
- 0% of known issues have a published fixed version.
- Remediation: pip install --upgrade chromadb
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed May 18, 2026, most recently Jun 12, 2026 (25 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-45829 ChromaDB Python project has a pre-authentication code injection vulnerability | CRITICAL | 1.0.0, 1.0.10, 1.0.11, 1.0.12 (+40 more) | No fix available |
| CVE-2026-45833 ChromaDB has a code injection vulnerability | CRITICAL | 0.4.17, 0.4.18, 0.4.19, 0.4.20 (+72 more) | No fix available |
About This Data
Vulnerability data for chromadb is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related PyPI (Python) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of chromadb.