ChromaDB
Records
6
Disclosed CVEs
6
Exploited (sev 3–4)
0
CISA KEV flagged
0
Newest record 2026-06-12 · 6 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Patch now: confirmed exploitation or KEV · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for ChromaDB has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
▂█
Nov ’246 disclosed · peak 5 in Jun ’26Oct ’26
Disclosed CVEs, no confirmed exploitation · 6
- 2026-06-12CVE-2026-45832CVE-2026-45832: Authorization control bypass in ChromaDB Python project endpoints2 Disclosedchromadb · authorization-bypass
- 2026-06-12CVE-2026-8828CVE-2026-8828: Authorization validation flaw in ChromaDB Rust project2 Disclosedchromadb · authorization-bypass
- 2026-06-12CVE-2026-45830CVE-2026-45830: ChromaDB cross-tenant access vulnerability2 Disclosedauthorization · chromadb
- 2026-06-12
- 2026-06-12
- 2026-05-18CVE-2026-45829ChromaDB Python Project Contains Pre-Authentication Code Injection Vulnerability2 Disclosedcode-injection · chromadb
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.