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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 5
https://github.com/chroma-core/chroma
disclosure@vulncheck.com
https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/get_collecti…
disclosure@vulncheck.com
https://github.com/chroma-core/chroma/blob/1.5.9/rust/frontend/src/server.rs#L4…
disclosure@vulncheck.com
https://github.com/chroma-core/chroma/issues/7462
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/chroma-through-1.5.9-authorization-bypass-…
disclosure@vulncheck.com