ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection
CVE-2026-45830 · GHSA-2wm9-hf6c-p5cr · published 2026-06-12 · updated 2026-08-24
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 0.34%
- Fixed in
- No fix yet
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection regardless of which tenant they belong to.
No fixed release is listed yet for chromadb. Limit what it can reach, or stop using it until a fix ships, and follow the source advisory for updates.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| chromadb | PyPI | >= 0.4.17, <= 1.5.9 | No fix yet |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.