Is there a public exploit for CVE-2026-45833?

Yes. Proof-of-concept code for CVE-2026-45833 has been published publicly.

Is there a proof of concept for CVE-2026-45833?

Yes — 1 proof-of-concept entry is linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-45833?

CVE-2026-45833 scores CVSS 9.4 (v4.0), rated critical. EPSS puts the chance of exploitation in the next 30 days at 0.34%.

What does CVE-2026-45833 affect?

CVE-2026-45833 affects Chroma chromadb. It is part of the AI and agent stack (Chroma).

9.4 Critical

A code injection vulnerability in version 0.4.17 or later of the ChromaDB Python project allows an authenticated attacker to run arbitrary…

CVE-2026-45833

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 trustremotecode set to true in the /api/v2/tenants/defaulttenant/databases/defaultdatabase/collections/{collectionid} if they have the UPDATECOLLECTION permission.

Proof-of-concept code is published

Public PoC

Public PoCe4zyy/Project-CVE-2026-45833

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Part of the AI stack

This affects Chroma, in Vector & retrieval.

Assessment

CVSS: 9.4 (v4.0)
Severity: Critical
EPSS: 0.34% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC
Published: 12 June 2026
Last updated: 26 October 2026
Affected: Chroma · ChromaDB · chromadb
Weakness: CWE-94
Assigner: 6f8de1f0-f67e-45a6-b68f-98777fdb759c

CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 5 + 3? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-45833