high · CVSS v3 8.1 · CVSS v4 8.6
CVE-2026-92782
Chroma versions up to and including 1.5.9 contain an authorization bypass vulnerability within its collection resolution logic. Authenticate
Overview
Chroma versions up to and including 1.5.9 contain an authorization bypass vulnerability within its collection resolution logic. Authenticated users can read, modify, or update vector collections belonging to other tenants if the target collection identifier is known. This flaw effectively breaks multi-tenant data isolation boundaries.
Description
Chroma through 1.5.9 fails to validate tenant and database segments when resolving collections, allowing authenticated attackers to access collections from other tenants by knowing the collection identifier. Attackers can read, modify, and update records in foreign collections by issuing requests under their own tenant path, bypassing authorization checks.
Impact
Impacts deployments utilizing Chroma as a multi-tenant vector database. Confidentiality and integrity are impacted, as authenticated users can view, alter, and overwrite data belonging to foreign tenants without authorization.
Remediation
Upgrade Chroma to a version newer than 1.5.9 that includes patched authorization validation for tenant and database segments. If patching immediately is not possible, enforce tenant validation upstream using an API gateway or middleware service to verify collection ownership before routing requests.
Risk context
Carries High severity with a CVSS v3 score of 8.1 and CVSS v4 score of 8.6. While EPSS scores are not yet available, the vulnerability poses significant operational risk for multi-tenant AI/ML application infrastructure.
Affected products
- Chroma
- ChromaDB
Scores
- Severity
- high
- CVSS v2
- 8.5
- CVSS v3
- 8.1
- CVSS v4
- 8.6
- EPSS
- —