CVE-2026-45832: ChromaDB authorization bypass in V1 collection endpoints

CVE-2026-45832 · 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 legacy V1 interface allows any logged-in user to bypass data isolation controls. This means an attacker could view or modify private data belonging to other customers or departments, potentially leading to large-scale data breaches or unauthorized data manipulation.

Quick answers

Is CVE-2026-45832 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45832 being exploited in the wild.
How severe is CVE-2026-45832?
Informational severity, with a CVSS score of 8.8, published 12 June 2026.
Which products and versions are affected?
ChromaDB ChromaDB 0.5.0 to latest Python release.
Is there a fix for CVE-2026-45832?
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-45832 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-45832?
Check whether anything you run is named in the advisory. 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

A missing authorization vulnerability exists in ChromaDB's FastAPI implementation within `chromadb/server/fastapi/__init__.py`. The V1 collection-level endpoints (such as add_v1 and get_v1) systematically pass `None` for the tenant and database parameters when calling the authorization sync method. This causes the `AuthzResource` to be initialized without tenant context, rendering tenant-scoped access controls ineffective regardless of the configured authorization provider. An authenticated attacker can exploit this by targeting collections via their UUID through these V1 endpoints to achieve unrestricted read/write access across the entire database. As of the advisory date, the V1 API cannot be disabled, and no patch has been confirmed by the vendor.

Affected products

  • ChromaDB ChromaDB 0.5.0 to latest Python release

Timeline

  • 2026-02-17: disclosed: Initial disclosure to ChromaDB security team
  • 2026-06-12: advisory: Public disclosure by HiddenLayer

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.