CVE-2026-45829: ChromaDB's Python FastAPI server runs an attacker's model code before checking authentication (CVSS 4.0 10.0), no fix in 1.5.9
ChromaDB CVE-2026-45829: one unauthenticated create-collection request runs attacker Python on the Python FastAPI server
Analysis
HiddenLayer discovered CVE-2026-45829 in ChromaDB's Python FastAPI server and gave it the maximum severity score (BleepingComputer, 2026-05-19); Hadrian, which published a technical analysis the same day, gives CVSS 4.0 10.0 and repeats HiddenLayer's name for it, "ChromaToast", (Hadrian, 2026-05-19). The create-collection handler loads the request's embedding-function configuration before it checks authentication: with trust_remote_code set to true and model_name pointed at a HuggingFace repository or local path the attacker controls, the server downloads and instantiates the model and runs the attacker's Python inside the uvicorn server process (Hadrian, 2026-05-19), and only then rejects the request, with a 500 in HiddenLayer's description (BleepingComputer, 2026-05-19). Every Python FastAPI server from 1.0.0 is affected while the default Rust frontend does not use this code path, and there was no fixed version at the time of writing, 1.5.9 being the latest (Hadrian, 2026-05-19). HiddenLayer reports an initial acknowledgement on 2025-12-16 followed by silence across more than ten follow-ups (Hadrian, 2026-05-19), and its Shodan queries found roughly 73% of internet-exposed instances running a vulnerable version (BleepingComputer, 2026-05-19); Hadrian dates the report to 2025-11-28 (Hadrian, 2026-05-19), BleepingComputer to February 17 (BleepingComputer, 2026-05-19).
Triage: HuggingFace downloads started by your own ingestion code are normal; the same download from the Chroma server process that your ingestion code did not initiate is the signal (Hadrian, 2026-05-19).
Cited evidence
Only the Python server is affected. The Rust server doesn't go through this code path.
There is no fixed version at time of writing (latest is 1.5.9).
The server rejects the request, returns a 500, and the attacker's payload has already run.
Updates1
No server-wide setting turns trust_remote_code off: the flag travels in the attacker's own create-collection request, inside the embedding-function arguments (Hadrian, 2026-05-19), and the sourced mitigations are the Rust frontend, keeping the Python server off public networks and restricting access to the API port (BleepingComputer, 2026-05-19). The rejection that follows the payload is a 500 in HiddenLayer's description (BleepingComputer, 2026-05-19) and in Hadrian's own proof of concept, although Hadrian's summary says 403 (Hadrian, 2026-05-19). HiddenLayer discovered and scored the flaw (BleepingComputer, 2026-05-19), and Hadrian published the technical analysis (Hadrian, 2026-05-19).
Sources2
Revision history
- Published 2026-05-21-77cdc4cd
- Correction 2026-10-21T1148Z-audit
ChromaDB has no server-wide switch that disables trust_remote_code, since the flag arrives in the attacker's own request; the sourced mitigations are the Rust frontend, no public exposure of the Python server and restricted access to the API port. The rejection after the payload runs is a 500 in HiddenLayer's account and Hadrian's proof of concept. HiddenLayer discovered and scored the flaw, and Hadrian published the technical analysis.
Changed: actions affected_products body classification cves evidence headline sectors sources sourcing_note summary techniques title
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.