CVE-2026-45833
Description
A flaw was found in the ChromaDB Python project. An authenticated attacker with UPDATE_COLLECTION permission could exploit a code injection vulnerability. By sending a malicious model repository to a specific API endpoint with trust_remote_code enabled, the attacker can execute arbitrary code on the server. This could lead to a complete compromise of the affected system.
Statement
This is a post-authentication ChromaDB FastAPI flaw: exploitation requires a valid user with UPDATE_COLLECTION and a crafted request that sets trust_remote_code: true on a malicious HuggingFace model. It is not unauthenticated remote code execution.
RH AI products ship a vulnerable chromadb version but do not expose the Chroma FastAPI API as the default product surface. RHOAI AutoRAG uses Llama Stack with Milvus/pgvector; RHEL AI bootc images include chromadb as a library dependency, not a network-facing Chroma server. Without a customer or misconfiguration that runs and exposes the Chroma Python server to untrusted users, the upstream attack path is not reachable.
Upstream CVSS 9.4 Critical assumes network access to Chroma’s API with exploitable permissions. That does not match default RHOAI/RHEL AI architecture, so Important is the appropriate RH impact.
Mitigation
To mitigate this issue, ensure that the `trust_remote_code` setting in ChromaDB is disabled. This setting prevents the execution of arbitrary code from remote model repositories. Consult ChromaDB documentation for specific configuration instructions to disable `trust_remote_code`. If the ChromaDB service is restarted or reloaded, verify that the setting remains disabled.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | 8.8 | 7.5 |
| Attack Vector | Network | Network | Network |
| Attack Complexity | High | Low | High |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | High | High | High |
| Integrity Impact | High | High | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can also lead to loss of data integrity in nearly all cases, since the control-plane data injected is always incidental to data recall or writing.
Non-Repudiation
Technical Impact: Hide Activities
Often the actions performed by injected control code are unlogged.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
