Security readout for executives and security teams
Plain-English summary
CVE-2026-45829 affects the ChromaDB Python project and is described as pre-authentication code injection. An unauthenticated attacker could cause the server to run code by abusing model repository handling with trust_remote_code enabled through a collections API endpoint. Business risk is server compromise where affected ChromaDB APIs are reachable.
Executive priority
Treat this as urgent for any exposed ChromaDB deployment. The potential impact is full server compromise before authentication. Prioritize exposure reduction now, then track vendor remediation and upgrade guidance.
Technical view
The bundle describes ChromaDB 1.0.0 or later as vulnerable through /api/v2/tenants/{tenant}/databases/{db}/collections when a malicious model repository is supplied and trust_remote_code is true. It is mapped to CWE-502 and CWE-94 with CVSS 4.0 score 10.0, network attack vector, no privileges, and no user interaction.
Likely exposure
Highest concern is internet-reachable or broadly internal ChromaDB API deployments running affected chromadb versions. Exposure depends on whether the relevant collections endpoint is reachable by unauthenticated users and whether requests can enable trust_remote_code with external model repositories.
Exploitation context
The source bundle does not report CISA KEV listing or confirmed active exploitation. The described attack is pre-authentication and network reachable, so exploitability risk is high where the API is exposed. Evidence provided is sufficient for urgent assessment but incomplete on patch status.
Researcher notes
Do not assume every ChromaDB instance is exploitable without confirming version, endpoint reachability, and trust_remote_code behavior. The bundle’s affected-version wording is inconsistent, listing 1.0.0 while describing 1.0.0 or later. Patch status is not established in the supplied evidence.
Mitigation direction
- Identify all ChromaDB deployments and remove unauthenticated network exposure immediately.
- Block or tightly restrict the affected collections API at proxies or gateways.
- Prevent trust_remote_code=true for untrusted or external model repositories where enforceable.
- Check Chroma project guidance and issue 6717 for fixed versions or official remediation.
- Apply vendor updates once a fixed release is confirmed by official sources.
Validation and detection
- Inventory chromadb package versions and flag deployments at 1.0.0 or later.
- Map all reachable ChromaDB API endpoints from internet and internal networks.
- Review gateway and application logs for collections API requests using trust_remote_code=true.
- Check whether model repository inputs can reference untrusted remote locations.
- For Red Hat environments, review the Red Hat CVE and CSAF VEX entries.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45829 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——HiddenLayerCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96redhat-SADPVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: 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
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-18T17:00:55.638Z: Reported to Red Hat.
- 2026-05-18T15:59:22.529Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.hiddenlayer.com/research/chromatoast-served-pre-authCVE reference, HiddenLayer
- https://github.com/chroma-core/chroma/issues/6717CVE reference, HiddenLayer
- https://access.redhat.com/security/cve/CVE-2026-45829CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2479623CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45829.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.