# CVE-2026-8828: ChromaDB Rust project IDOR in collection lookup

Source: https://junglewise.ai/threats/cve-2026-8828-chromadb-rust-project-idor-in-collection-lookup  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-12. Updated: 2026-06-12  
License: CC BY 4.0 with a link back

CVE-2026-8828 · Severity: info · CVSS 8.8 · Published 2026-06-12

ChromaDB is an open-source vector database used to store and manage data for AI applications. A security flaw in its Rust-based components allows any logged-in user to access, modify, or delete data belonging to other customers (tenants) if they know the unique identifier for a data collection. This could lead to unauthorized data exposure or loss in shared environments where multiple organizations use the same database infrastructure.

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

## Quick answers

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

**How severe is CVE-2026-8828?** Informational severity, with a CVSS score of 8.8, published 12 June 2026.

**Which products and versions are affected?** Chroma 1.0.0 or later.

**Is there a fix for CVE-2026-8828?** 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-8828 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-8828?** 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

An Insecure Direct Object Reference (IDOR) vulnerability exists in the Rust-based frontend and backend implementations of ChromaDB (including SQLite and Spanner backends). The root cause is that collection lookups performed via UUID skip tenant and database validation filters. In the Rust SQLite backend, the database parameter is dropped during the `get_collection_with_segments` call, while the Spanner backend's SQL query lacks a tenant filter clause entirely. An attacker with network access and valid credentials can bypass tenant isolation to manipulate any collection by providing its UUID. This affects distributed deployments and Chroma Cloud environments.

## Affected products

- ChromaDB ChromaDB Rust project 1.0.0 or later

## Timeline

- 2026-02-17: disclosed: Initial disclosure to ChromaDB vendor.
- 2026-05-18: other: Public disclosure of a related vulnerability after no vendor response.
- 2026-06-12: advisory: Full advisory published by HiddenLayer.

## References

- [https://www.hiddenlayer.com/sai-security-advisory/2026-06-chromadb-2](https://www.hiddenlayer.com/sai-security-advisory/2026-06-chromadb-2)

## Related threats

- [Chroma authorization bypass in collection access](https://junglewise.ai/threats/cve-2026-92782-chroma-authorization-bypass-in-collection-access)
- [Chroma input validation flaw in HNSW index parameters](https://junglewise.ai/threats/cve-2026-85664-chroma-input-validation-flaw-in-hnsw-index-parameters)
- [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)