CVE-2026-45833: A code injection vulnerability in version 0.4.17 or later of the ChromaDB Python project allows an authenticat

Q: How do I fix CVE-2026-45833?

chromadb: upgrade to newer than 1.5.9. Exact commands for each OS are on this page.

Q: Is CVE-2026-45833 being exploited?

CVE-2026-45833 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-45833 affect?

CVE-2026-45833 affects chromadb. Severity is high (CVSS 8.8). 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 /

Routine

HIGH 8.8UPGRADE

CVE-2026-45833 is a high-severity flaw (CVSS 8.8) affecting chromadb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-94
Published	2026-06-12
Last modified	2026-10-26

Publisher (CNA): HiddenLayer · Vendor: trychroma

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-12 16:16 UTCPublished CVE record published
2026-10-26 11:10 UTCUpdated Record last modified

trychroma chromadb UPGRADE

Affected: >= 0.4.17 and <= 1.5.9

Fixed in: newer than 1.5.9

Safe to downgrade to: a release before 0.4.17

1. Check installed version

pip show chromadb

2. UPGRADE to newer than 1.5.9

pip install --upgrade "chromadb>1.5.9"

3. If no update is available yet, DOWNGRADE to a release before 0.4.17

pip index versions chromadb pip install "chromadb<0.4.17"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-45833?

chromadb: upgrade to newer than 1.5.9. Exact commands for each OS are on this page.

Is CVE-2026-45833 being exploited?

CVE-2026-45833 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-45833 affect?

CVE-2026-45833 affects chromadb. Severity is high (CVSS 8.8). 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 /

How urgent is CVE-2026-45833?

Priority 38/100. High severity

Software pages

Python vulnerabilities

Related CVEs

CVE-2026-45830 HIGH 8.8 UPGRADE A lack of authorization validation in version 0.4.17 or later of the ChromaDB Python project allows any authen
CVE-2026-45832 HIGH 8.8 UPGRADE All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the au
CVE-2026-45831 HIGH 8.8 UPGRADE The SimpleRBACAuthorizationProvider authorization provider in versions 0.5.0 or later of the ChromaDB Python p

References

← Back to latest CVEs