What is CVE-2026-45829?
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 record classifies CVE-2026-45829 under weakness class CWE-94. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 163 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 10 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - CVSS v4.0 base score
- 10
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H - EPSS (FIRST)
- 1.0% probability of exploitation in the next 30 days, higher than 62.4% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 9.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-18, last modified 2026-07-15
Is CVE-2026-45829 being exploited?
Weaponised exploit code for CVE-2026-45829 is publicly available. 2 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 29 in the Threadlinqs vulnerability feed.
Affected products and versions
- Chroma: ChromaDB
How to fix CVE-2026-45829
No vendor patch reference has been recorded for CVE-2026-45829 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-45829
1 tracked threat in the Threadlinqs corpus references CVE-2026-45829, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on .