Chroma: ChromaDB Python project has a pre-authentication code injection vulnerability
Chroma
More for Chroma RSS feed for Chroma
- Severity
- Critical, CVSS 10.0
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Record
- CVE-2026-45829
- Affects
- Chroma
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- May 18, 2026
- Source last modified
- October 5, 2026
Description
A pre-authentication, code injection vulnerability in version 1.0.0 or later of the ChromaDB Python project allows an unauthenticated attacker to run arbitrary code on the server by sending a malicious model repository and trust_remote_code set to true in the /api/v2/tenants/{tenant}/databases/{db}/collections endpoint.
Description quoted from the NVD record.
Who is affected
Chroma (also called ChromaDB) is a database that stores information so AI applications can search it by meaning. This flaw affects Chroma's Python package, version 1.0.0 or later. It is in the part of the product that creates collections, the groups where stored data is kept. An attacker who has not logged in can send a request that points to a harmful AI model source, along with a setting that allows outside code to run. The attacker can then run any code they choose on the server running Chroma. This flaw is rated Critical.
What to do
- Find out whether your organization uses Chroma, and who installed it or runs it.
- If someone on your staff runs Chroma, ask them to check whether it is version
1.0.0or later. - No fixed version is named for this flaw yet. The person who runs Chroma should check the vendor advisory linked on this page for a fixed release and install it as soon as it is available.
- If an IT provider or vendor runs Chroma for your organization, send them this advisory and ask when the update will be done.
Analysis written from the source record as of October 5, 2026 and reviewed before publishing.