EUVD-2026-81045
GHSA-j8fq-8cc8-m22c
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable API, low complexity, but needs a valid low-privileged tenant account (PR:L); high confidentiality and integrity from cross-tenant read/write, no availability impact, scope unchanged.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Incorrect authorization in Chroma through 1.5.9 allows any authenticated user to read, modify, and update records inside collections belonging to other tenants, simply by issuing requests under their own tenant path while naming a collection identifier that belongs to a foreign tenant. The flaw exists because the collection-resolution path never validates the tenant and database segments, so the co-tenant boundary is effectively absent - this is a real, meaningful risk but bounded by an authentication requirement (PR:L) and by the attacker's need to know or enumerate a valid foreign collection identifier. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires an authenticated Chroma account (PR:L) on an instance shared across multiple tenants, and knowledge of a target collection identifier belonging to another tenant. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Real, meaningful risk but bounded by an authentication requirement. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No vendor-released patch is identified at time of analysis, so track https://github.com/chroma-core/chroma/issues/7462 and the project repository at https://github.com/chroma-core/chroma for a fixed release, and upgrade beyond 1.5.9 as soon as one is published and validated against the tenant/database validation path in the Rust frontend. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every Chroma deployment, confirm which run 1.5.9 or earlier, and identify any single instance shared across a trust boundary (multiple tenants, customers, business units, or environments); for those instances, restrict network reachability of the Chroma API to known application callers only, suspend direct user-facing access to collection APIs, and enable request logging that captures tenant and collection identifiers so cross-tenant access attempts become detectable; if isolation cannot be achieved immediately, migrate the most sensitive tenants to dedicated single-tenant Chroma deployments. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Command injection via Windows CreateProcess argument parsing affects multiple language runtimes and tooling (Node.js, PH
In the standard library in Rust before 1.52.0, a double free can occur in the Vec::from_iter function if freeing the ele
In the standard library in Rust before 1.52.0, the Zip implementation can report an incorrect size due to an integer ove
library/std/src/net/parser.rs in Rust before 1.53.0 does not properly consider extraneous zero characters at the beginni
The Rust Programming Language Standard Library 1.34.x before 1.34.2 contains a stabilized method which, if overridden, c
In the standard library in Rust before 1.52.0, the Zip implementation calls __iterator_get_unchecked() more than once fo
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe c
Cargo prior to Rust 1.26.0 may download the wrong dependency if your package.toml file uses the `package` configuration
Rust is a programming language. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no auth
The Rust Programming Language Standard Library version 1.29.0, 1.28.0, 1.27.2, 1.27.1, 127.0, 126.2, 126.1, 126.0 contai
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. Rated medium severity (C
The Rust Programming Language Standard Library 1.18.0 and later is affected by: CWE-200: Information Exposure. Rated med
Same weakness CWE-863 – Incorrect Authorization
View allShare
External POC / Exploit Code
Leaving vuln.today