# CVE-2026-45833: ChromaDB has a code injection vulnerability

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

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-36p7-vc44-83pf, PYSEC-2026-3814

## What is CVE-2026-45833?

CVE-2026-45833 is a critical code injection vulnerability in ChromaDB, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A code injection vulnerability in version 0.4.17 or later of the ChromaDB Python project allows an authenticated 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/default_tenant/databases/default_database/collections/{collection_id} if they have the UPDATE_COLLECTION permission.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

3 open source packages ship an affected version, including chromadb. It affects 1 product.


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

Products: Trychroma Chromadb.

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

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

## Is CVE-2026-45833 being exploited?

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

Public exploit code:

- CVE-2026-45833 ChromaDB  (github_poc): https://github.com/e4zyy/Project-CVE-2026-45833

## Other vulnerabilities in ChromaDB

- [CVE-2026-45830](https://insights.sbomify.com/CVE-2026-45830/): ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collection (high 8.8)
- [CVE-2026-45831](https://insights.sbomify.com/CVE-2026-45831/): ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies to (high 8.8)
- [CVE-2026-45832](https://insights.sbomify.com/CVE-2026-45832/): Auth bypass in ChromaDB (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45833 is a critical code injection vulnerability in ChromaDB, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45833 exists.

Affected packages and fixed versions:
- chromadb (PyPI): affected from 0.4.17 up to 1.5.9; no fix listed
- chromadb (PyPI): affected from 0.4.17 up to 1.5.9; no fix listed
- chromadb (PyPI): affected from 0.4.17 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-45833/ (Markdown: https://insights.sbomify.com/CVE-2026-45833/index.md)
```

## Sources

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

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