CVE-2026-45832: Authorization control bypass in ChromaDB Python project endpoints
ChromaDB
ChromaDB's Python project passes null values for tenant and database parameters on V1 collection-level endpoints, bypassing authorization controls. No known real-world exploitation has been documented.
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 79% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 12 Jun 2026
- last update
- 12 Jun 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-06-12CVE-2026-45832: All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the authorization layer,…NVD · nvd.nist.gov/vuln/detail/CVE-2026-45832
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
- NVDVulnerability 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 10:04Z · 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-45832: Authorization control bypass in ChromaDB Python project endpoints https://gcdradar.vercel.app/incidents/cve-2026-45832-authorization-control-bypass-in-chromadb-pyth · AIR-2026-1110 · 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-45832 - CVSS: 8.8 ## Summary ChromaDB's Python project passes null values for tenant and database parameters on V1 collection-level endpoints, bypassing authorization controls. No known real-world exploitation has been documented. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-06-12: CVE-2026-45832: All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the authorization layer,… (https://nvd.nist.gov/vuln/detail/CVE-2026-45832) ## Sources - 2026-06-12 NVD: CVE-2026-45832: All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the authorization layer,… https://nvd.nist.gov/vuln/detail/CVE-2026-45832 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- 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-45830: ChromaDB cross-tenant access vulnerability
Patch now · Disclosed · since 12 Jun 2026 · CVE-2026-45830
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