Chroma ChromaDB up to 0.4.17 Model collections code injection

Summaryinfo

A vulnerability identified as critical has been detected in Chroma ChromaDB up to 0.4.17. Impacted is an unknown function of the file /api/v2/tenants/default_tenant/databases/default_database/collections of the component Model Handler. Performing a manipulation results in code injection. This vulnerability is reported as CVE-2026-45833. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Chroma ChromaDB up to 0.4.17. It has been classified as critical. This affects some unknown functionality of the file /api/v2/tenants/default_tenant/databases/default_database/collections of the component Model Handler. The manipulation with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at hiddenlayer.com. This vulnerability is uniquely identified as CVE-2026-45833 since 05/13/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/12/2026). MITRE ATT&CK project uses the attack technique T1059 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Chroma

Name

• ChromaDB

Version

• 0.4.0
• 0.4.1
• 0.4.2
• 0.4.3
• 0.4.4
• 0.4.5
• 0.4.6
• 0.4.7
• 0.4.8
• 0.4.9
• 0.4.10
• 0.4.11
• 0.4.12
• 0.4.13
• 0.4.14
• 0.4.15
• 0.4.16
• 0.4.17

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion