Is CVE-2026-45833 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-45833 being exploited in the wild.

How severe is CVE-2026-45833?

Critical severity, with a CVSS score of 4, published 12 June 2026.

Which products and versions are affected?

chromadb (PyPI) >= 0.4.17, <= 1.5.9, ECOSYSTEM:introduced=0.4.17,last_affected=1.5.9.

Is there a fix for CVE-2026-45833?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-45833 attacked?

It is attacked over the network.

Am I affected by CVE-2026-45833?

Check whether you run chromadb (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45833: ChromaDB code injection in update_collection endpoint

Q: Is there a fix for CVE-2026-45833?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-45833 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-45833?

Check whether you run chromadb (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45833 · Severity: critical · CVSS 4 · Published 2026-06-12

ChromaDB is a vector database system used for storing and querying embeddings in AI applications. An authenticated user with collection update privileges can upload a malicious embedding model that executes arbitrary code on the server when loaded. This could allow attackers to steal sensitive data, modify database contents, or pivot to attack other systems on the network.

Technologies: chromadb (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-45833 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-45833 being exploited in the wild.
How severe is CVE-2026-45833?: Critical severity, with a CVSS score of 4, published 12 June 2026.
Which products and versions are affected?: chromadb (PyPI) >= 0.4.17, <= 1.5.9, ECOSYSTEM:introduced=0.4.17,last_affected=1.5.9.
Is there a fix for CVE-2026-45833?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-45833 attacked?: It is attacked over the network.
Am I affected by CVE-2026-45833?: Check whether you run chromadb (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a code injection flaw (CWE-94) in ChromaDB's update_collection API endpoint. When a user updates a collection's embedding function configuration, ChromaDB instantiates the specified model using the HuggingFace Transformers library. If trust_remote_code is set to true, this allows arbitrary Python code from the remote model repository to execute with the privileges of the ChromaDB server process. The vulnerability requires network access to the API and valid authentication with UPDATE_COLLECTION permission, but does not require additional user interaction. The model instantiation code path is reached after authentication checks, making this a post-authentication RCE vulnerability. No patch versions have been released to date; mitigation involves disabling the trust_remote_code setting in ChromaDB configuration.

Affected products

ChromaDB chromadb 0.4.17 to 1.5.9

Identifiers

CVE-2026-45833
GHSA-36p7-vc44-83pf
PYSEC-2026-3814

Timeline

2026-02-17: disclosed: Initial disclosure to ChromaDB security team
2026-06-12: advisory: Public disclosure via GitHub Security Advisory and NVD
2026-08-24: other: Advisory updated

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.