Chroma ChromaDB up to 1.0.0 Model collections code injection

Summaryinfo

A vulnerability classified as critical has been found in Chroma ChromaDB up to 1.0.0. This issue affects some unknown processing of the file the /api/v2/tenants/{tenant}/databases/{db}/collections of the component Model Handler. This manipulation causes code injection. The identification of this vulnerability is CVE-2026-45829. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Chroma ChromaDB up to 1.0.0. It has been declared as critical. Affected by this vulnerability is some unknown processing of the file the /api/v2/tenants/{tenant}/databases/{db}/collections of the component Model Handler. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A pre-authentication, code injection vulnerability in version 1.0.0 or later of the ChromaDB Python project allows an unauthenticated 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/{tenant}/databases/{db}/collections endpoint.

The weakness was shared by Esteban Tonglet as 6717. The advisory is shared at hiddenlayer.com. This vulnerability is known as CVE-2026-45829 since 05/13/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 05/18/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

• 1.0

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