# CVE-2026-45829: ChromaDB Python project has a pre-authentication code injection vulnerability

> An unauthenticated attacker can execute arbitrary code on the server by sending a malicious model repository with trust_remote_code enabled.

- **Severity:** Critical 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-f4j7-r4q5-qw2c, PYSEC-2026-311

## What is CVE-2026-45829?

CVE-2026-45829 is a critical code injection vulnerability in ChromaDB, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-45829?

3 open source packages ship an affected version, including chromadb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chromadb` | PyPI | From 1.0.0 to 1.5.9 | None |
| `chromadb` | PyPI | From 1.0.0 to 1.5.9 | None |
| `chromadb` | PyPI | From 1.0.0 to 1.5.9 | None |

## How do I fix CVE-2026-45829?

No fix has been published for CVE-2026-45829 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45829 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45829 exists.

Public exploit code:

- Analisis completo y PoC de CVE-2026-45829 en ChromaDB. (github_poc): https://github.com/fevar54/FULL-ANALYSIS---CVE-2026-45829-ChromaDB-
- CVE-2026-45829 (github_poc): https://github.com/0xredash/CVE-2026-45829

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45829 and fix it if it is affected.

What it is: CVE-2026-45829 is a critical code injection vulnerability in ChromaDB, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45829 exists.

Affected packages and fixed versions:
- chromadb (PyPI): affected from 1.0.0 up to 1.5.9; no fix listed
- chromadb (PyPI): affected from 1.0.0 up to 1.5.9; no fix listed
- chromadb (PyPI): affected from 1.0.0 up to 1.5.9; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45829/ (Markdown: https://insights.sbomify.com/CVE-2026-45829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45829
- OSV: https://osv.dev/vulnerability/CVE-2026-45829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45829/
Summaries are generated and may contain mistakes; the official description above is the record.