CVE-2026-45830: ChromaDB cross-tenant access vulnerability
ChromaDB
A lack of proper authorization validation in ChromaDB enables any authenticated user to arbitrarily read, write, update, or delete data in collections across any tenant. The vulnerability compromises tenant isolation in shared vector database setups.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 8.8
- EPSS
- <0.01 · top 72% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 12 Jun 2026
- last update
- 12 Jun 2026
- CVE ids
Timeline · 2
Sources · 2
Advisories and databases
- 2026-06-12CVE-2026-45830: ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collectionGitHub Advisory Database · github.com/advisories/GHSA-2wm9-hf6c-p5cr
- 2026-06-12CVE-2026-45830: A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to…NVD · nvd.nist.gov/vuln/detail/CVE-2026-45830
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 12 Jun 2026 · first reported 12 Jun 2026
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-45830: ChromaDB cross-tenant access vulnerability https://gcdradar.vercel.app/incidents/cve-2026-45830-chromadb-cross-tenant-access-vulnerability · AIR-2026-0730 · closed 2026-06-12 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-06-12 - AI role: Attack on AI - Products: ChromaDB - CVE ids: CVE-2026-45830 - CVSS: 8.8 ## Summary A lack of proper authorization validation in ChromaDB enables any authenticated user to arbitrarily read, write, update, or delete data in collections across any tenant. The vulnerability compromises tenant isolation in shared vector database setups. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-06-12: CVE-2026-45830: A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to… (https://nvd.nist.gov/vuln/detail/CVE-2026-45830) - 2026-06-12: CVE-2026-45830: ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection (https://github.com/advisories/GHSA-2wm9-hf6c-p5cr) ## Sources - 2026-06-12 GitHub Advisory Database: CVE-2026-45830: ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection https://github.com/advisories/GHSA-2wm9-hf6c-p5cr - 2026-06-12 NVD: CVE-2026-45830: A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to… https://nvd.nist.gov/vuln/detail/CVE-2026-45830 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.8ChromaDB CVE-2026-45832: Authorization control bypass in ChromaDB Python project endpoints
Patch now · Disclosed · since 12 Jun 2026 · CVE-2026-45832
AI - closed8.8ChromaDB CVE-2026-8828: Authorization validation flaw in ChromaDB Rust project
Patch now · Disclosed · since 12 Jun 2026 · CVE-2026-8828
AI - closed8.8ChromaDB CVE-2026-45831: ChromaDB authorization provider flaw
Patch now · Disclosed · since 12 Jun 2026 · CVE-2026-45831
AI - closed9.4ChromaDB CVE-2026-45833: ChromaDB code injection vulnerability
Patch now · Disclosed · since 12 Jun 2026 · CVE-2026-45833
AI - closed10.0ChromaDB ChromaDB Python Project Contains Pre-Authentication Code Injection Vulnerability
Patch now · Disclosed · since 18 May 2026 · CVE-2026-45829
AI - closed9.8Flowise Weak Hardcoded JWT Secrets in Flowise Authentication
Patch now · Disclosed · since 12 Jul 2026 · CVE-2026-56271
AI