Executive brief
Chroma is a search infrastructure platform that uses tenants and databases to isolate data collections. Due to insufficient authorization checks, authenticated users can access collections from other tenants by knowing the collection identifier, allowing them to read, modify, and delete data they should not have access to. This breaks data isolation guarantees in multi-tenant deployments.
Technical details
Chroma versions through 1.5.9 fail to validate tenant and database segments during collection resolution in the get_collection_with_segments_provider component. When an authenticated user requests a collection, the backend does not verify that the requesting user's tenant matches the collection's tenant, only validating against the collection ID. An attacker with valid credentials can craft requests under their own tenant path but reference collections from other tenants, bypassing authorization checks. This allows reading, modifying, and updating records in foreign collections. The vulnerability requires authentication and knowledge of target collection identifiers. A fix is likely available in versions after 1.5.9.
Affected products
- Chroma Chroma through 1.5.9
Timeline
- 2026-09-16: disclosed