Chroma through 1.5.9 Authorization Bypass via Collection Identifier
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| chroma-core | chroma | up to 1.5.9 | — | No fix listed | CNA |
- chroma Vendorchroma-core Affected up to 1.5.9 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-92782
- 2026-10-03 Alias added: GHSA-j8fq-8cc8-m22c
References
More chroma-core vulnerabilities
- TI-2026-58776 Chroma 1.5.9 Unbounded HNSW Index Parameters Memory Exhaustion CVSS 4.0HIGH 8.7
Sources
- CVE-2026-92782 · CVE Program
- CVE-2026-92782 · NVD
- FIRST EPSS
- GHSA-j8fq-8cc8-m22c · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences