CVE-2026-45830 ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection
Authenticated users can read, write, update, or delete data in any tenant's collection due to missing authorization checks in ChromaDB.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-45830?
CVE-2026-45830 is a high-severity missing authorization vulnerability in ChromaDB, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2026-45830?
3 open source packages ship an affected version, including chromadb. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
chromadb PyPI | From 0.4.17 to 1.5.9 | None |
chromadb PyPI | From 0.4.17 to 1.5.9 | None |
chromadb PyPI | From 0.4.17 to 1.5.9 | None |
Products include Trychroma Chromadb.
How do I fix CVE-2026-45830?
No fix has been published for CVE-2026-45830 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-45830 being exploited?
There is no known exploitation of CVE-2026-45830 in the wild and no public exploit code.
Other vulnerabilities in ChromaDB
Sources
Also known as GHSA-2wm9-hf6c-p5cr, PYSEC-2026-3813.