CVE-2026-45829 in the critical feed json
ChromaDB Python project has a pre-authentication code injection vulnerability
published 5mo ago modified 14d ago also EUVD-2026-30779 , GHSA-f4j7-r4q5-qw2c , PYSEC-2026-311
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.1%
- EPSS 15.1% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-45829 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-45829 updated cvss 10.0
chromadb: ChromaDB Python Project: Arbitrary code execution via pre-authentication code injection
-
Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
15.15% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- hiddenlayer.com https://www.hiddenlayer.com/research/chromatoast-served-pre-auth referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 10.0 | 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 |
| CISA ADP | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| CNA | 4.0 | 10.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | chromadb | >=1.0.0, <=1.5.9 |
no fix listed |
Affected products
- Chroma ChromaDB
- Red Hat Red Hat Enterprise Linux AI (RHEL AI) 3
Classification
References
-
hiddenlayer.com
/research/chromatoast-served-pre-auth
exploit, web
-
github.com
/chroma-core/chroma/issues/6717
web
-
access.redhat.com
/security/cve/CVE-2026-45829
vdb-entry, web
-
bugzilla.redhat.com
/show_bug.cgi?id=2479623
issue-tracking, web
- security.access.redhat.com /data/csaf/v2/vex/2026/cve-2026-45829.json
-
nvd.nist.gov
/vuln/detail/CVE-2026-45829
advisory
-
github.com
/advisories/GHSA-f4j7-r4q5-qw2c
advisory
-
github.com
/chroma-core/chroma
package
-
github.com
/pypa/advisory-database/tree/main/vulns/chromadb/PYSEC-2026-311.yaml
web
-
pypi.org
/project/chromadb
web, package
Sources
- CVE List CVE-2026-45829
- GitHub Advisory GHSA-f4j7-r4q5-qw2c
- NVD CVE-2026-45829
- OSV PYSEC-2026-311
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.