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

Published Sep 16, 2026
·
Updated

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.

Affected Software

1 affected component
Chroma<=1.5.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Chroma to a version that resolves this vulnerability.

    Fixed in 1.5.9

Event History

Sep 16, 2026
CVE Published
via MITRE·08:32 PM
Data Sourced
via MITRE·08:32 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated attacker can exploit it. They need to know the identifier of a collection belonging to another tenant; no user interaction is required.

2

What access could an attacker gain?

An attacker can access collections from other tenants despite making requests under their own tenant path. The described impact includes reading, modifying, and updating records in foreign collections.

3

Which versions are affected?

Chroma through version 1.5.9 is affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203