A 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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Public exploits 1
- e4zyy/Project-CVE-2026-45833 PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Change history 1
- First seenCVSS 9.4 · trychromaNVD modified 2026-10-26 11:10
Affected (CPE criteria) 1
cpe:2.3:a:trychroma:chromadb:*:*:*:*:*:python:*:*
References 5
- https://www.hiddenlayer.com/sai-security-advisory/2026-06-chromadb-5 Third Party Advisory
- https://access.redhat.com/security/cve/CVE-2026-45833
- https://bugzilla.redhat.com/show_bug.cgi?id=2488430
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45833.json
- https://www.hiddenlayer.com/sai-security-advisory/2026-06-chromadb-5 Third Party Advisory