Summary
Chroma through version 1.5.9 does not properly validate tenant and database segments when resolving collections. An authenticated attacker who knows a collection identifier may access, read, modify, or update records belonging to another tenant by submitting requests through their own tenant path.
Affected context
The vulnerability occurs in Chroma deployments that use tenant- and database-scoped collection resolution and rely on request path values to enforce isolation. It becomes risky when authorization checks do not verify that the resolved collection belongs to the authenticated tenant and database context.
Exploit preconditions
- Attack surface: Chroma collection access and management endpoints
- Required access: An authenticated account with permission to issue collection requests
- Trigger point: Collection resolution using attacker-controlled tenant and database segments
- Required knowledge: The identifier of a collection belonging to another tenant
- Why exploitation is possible: Tenant and database path values are not adequately validated against the collection's actual ownership before authorization is applied
Why this happens
The underlying flaw is an authorization boundary failure caused by incomplete validation of tenant and database identifiers during collection resolution. The application can resolve a foreign collection while processing a request under the attacker's own tenant path, allowing subsequent operations to bypass intended ownership checks. This behavior maps to CWE-863, Incorrect Authorization, because access-control decisions do not consistently enforce the resource's actual tenant and database scope.
Potential impact
- An attacker may read records from collections owned by other tenants.
- An attacker may modify or update foreign records.
- Tenant isolation may be weakened across shared Chroma deployments.
- Exposed data could support further privacy, integrity, or compliance impacts.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the resource
boundary rather than trusting request path segments.
Common defensive patterns include:
- Deriving tenant and database scope from authenticated server-side context where possible.
- Verifying that every resolved collection belongs to the requested tenant and database before allowing access.
- Applying centralized, deny-by-default authorization checks to read and write operations.
- Avoiding reliance on collection identifiers as proof of ownership.
- Limiting tenant privileges and separating sensitive workloads or databases where practical.
- Recording and reviewing cross-tenant access attempts and denied authorization decisions.
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review of collection lookup and authorization paths.
- Tests that attempt to access known resources across tenant and database boundaries.
- Review signals such as authorization checks performed before resource ownership is established.
- API policy enforcement requiring authenticated tenant context to match the resolved resource.
- Audit monitoring for collection operations where request scope and resource ownership differ.
Automated security testing and code review tools may help identify missing object-level authorization checks.

