Arbitrary Code Injection Affecting chromadb package, versions [0.4.17,]
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-CHROMADB-17337041
- published14 Jun 2026
- disclosed12 Jun 2026
- creditEsteban Tonglet
Introduced: 12 Jun 2026
NewCVE-2026-45833 (opens in a new tab)How to fix?
There is no fixed version for chromadb.
Overview
chromadb is a Chroma.
Affected versions of this package are vulnerable to Arbitrary Code Injection in the api/v2/tenants/default_tenant/databases/default_database/collections/{collection_id} endpoint when a malicious model repository is sent and trust_remote_code is set to true. An attacker can execute arbitrary code on the server by leveraging the UPDATE_COLLECTION permission and sending crafted requests.
Note: This is only exploitable if the attacker is authenticated and has the UPDATE_COLLECTION permission, and if trust_remote_code is enabled.