ChromadbApplication · Trychroma
CVE-2026-45833
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA code injection vulnerability in version 0.4.17 or later of the ChromaDB Python project allows an authenticated attacker to run arbitrary code on the server by sending a malicious model repository and trust_remote_code set to true in the /api/v2/tenants/default_tenant/databases/default_database/collections/{collection_id} if they have the UPDATE_COLLECTION permission.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA code injection vulnerability in ChromaDB Python versions 0.4.17+ allows authenticated users with UPDATE_COLLECTION permission to execute arbitrary code by supplying a malicious model repository with trust_remote_code=true to the collection API. The trust_remote_code parameter permits execution of arbitrary Python code from loaded model repositories, enabling complete server compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromadbApplication
>= 0.4.17, <= 1.5.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed ChromaDB versionRun 'pip show chromadb' or check your Python environment's installed package versionAffected if Version is >= 0.4.17 and <= 1.5.9
-
Check trust_remote_code configurationInspect your ChromaDB client configuration or environment settings for trust_remote_code parameterAffected if trust_remote_code is set to true or not explicitly set to false
-
Verify UPDATE_COLLECTION permission existsReview authentication/authorization configuration to determine if any user or service account has UPDATE_COLLECTION permission on collectionsAffected if UPDATE_COLLECTION permission is granted to any authenticated user or service
-
Check collections API exposureReview network access logs or API endpoint configuration for requests to the collections APIAffected if Collections API endpoint is network-accessible to authenticated users
User is affected if running ChromaDB 0.4.17-1.5.9 with trust_remote_code enabled and UPDATE_COLLECTION permission is available to authenticated users who can access the collections API.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedDisable or restrict the trust_remote_code parameter in ChromaDB configuration, implement strict validation of model repositories before loading, and review permission assignments for UPDATE_COLLECTION to limit exposure to only trusted administrators.
chromadb version > 1.5.9 (latest stable release)
- 1. Identify the current installed ChromaDB version using 'pip show chromadb' or 'pip list | grep chromadb'
- 2. Upgrade to the latest stable ChromaDB release that addresses this vulnerability (version > 1.5.9) using: pip install --upgrade chromadb
- 3. Verify the upgrade was successful: pip show chromadb
- 4. Review collection configurations to ensure trust_remote_code is set to false for any model repositories
- 5. If using ChromaDB in production, ensure appropriate authentication and authorization controls are in place to limit who has UPDATE_COLLECTION permissions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chromadb
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45833 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data