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

High 8.6 Published Updated

Authenticated attackers can access and modify other tenants' collections by bypassing authorization checks using known collection identifiers.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-92782?

CVE-2026-92782 is a high-severity missing authorization vulnerability in chroma-core chroma, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-863

Which versions are affected by CVE-2026-92782?

How do I fix CVE-2026-92782?

No fix has been published for CVE-2026-92782 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-92782 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92782 exists.

Sources

Also known as GHSA-j8fq-8cc8-m22c.

Is CVE-2026-92782 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free