# CVE-2026-92782: Chroma authorization bypass in collection access

Source: https://junglewise.ai/threats/cve-2026-92782-chroma-authorization-bypass-in-collection-access  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-16. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92782 · Severity: high · CVSS 8.1 · Published 2026-09-16

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.

Technologies: [Chroma](https://junglewise.ai/threats/technologies/chroma). Vendors: [Chroma](https://junglewise.ai/threats/vendors/chroma).

## Quick answers

**Is CVE-2026-92782 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92782 being exploited in the wild.

**How severe is CVE-2026-92782?** High severity, with a CVSS score of 8.1, published 16 September 2026.

**Which products and versions are affected?** Chroma through 1.5.9.

**Is there a fix for CVE-2026-92782?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92782 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-92782?** Check whether you run Chroma at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## 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

## References

- [https://github.com/chroma-core/chroma](https://github.com/chroma-core/chroma)
- [https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/get_collection_with_segments_provider.rs](https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/get_collection_with_segments_provider.rs)

## Related threats

- [Chroma input validation flaw in HNSW index parameters](https://junglewise.ai/threats/cve-2026-85664-chroma-input-validation-flaw-in-hnsw-index-parameters)
- [ChromaDB Rust project IDOR in collection lookup](https://junglewise.ai/threats/cve-2026-8828-chromadb-rust-project-idor-in-collection-lookup)
- [ChromaDB tenant isolation bypass via IDOR in collection lookup](https://junglewise.ai/threats/cve-2026-45830-chromadb-tenant-isolation-bypass-via-idor-in-collection-lookup)
- [Chroma ChromaDB code injection in Python backend server](https://junglewise.ai/threats/cve-2026-45829-chroma-chromadb-code-injection-in-python-backend-server)