Chroma vulnerabilities
We track 6 vulnerabilities in Chroma products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on June 12, 2026.
Latest Chroma vulnerabilities
- 8.8 High severity
ChromaDB: Authorization Bypass Through User-Controlled Key
A lack of authorization validation in version 1.0.0 or later of the ChromaDB Rust 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.
- 8.8 High severity
ChromaDB: Improper Control of Generation of Code
A code injection vulnerability in version 0.4.17 or later of the ChromaDB Python project allows an authenticated 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/defau
- 8.8 High severity
ChromaDB: Authorization Bypass Through User-Controlled Key
All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the authorization layer, allowing attackers to bypass authorization controls by using the V1 endpoints.
- 8.8 High severity
ChromaDB: Incorrect Authorization
The SimpleRBACAuthorizationProvider authorization provider in versions 0.5.0 or later of the ChromaDB Python project evaluates whether a user holds a given permission but never checks which tenant, database, or collection that permission applies to allowing us
- 8.8 High severity
ChromaDB: Authorization Bypass Through User-Controlled Key
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.
- 10.0 Critical severity
ChromaDB: Improper Control of Generation of Code
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