# ChromaDB Python project has a pre-authentication code injection vulnerability Advisory record · `GHSA-f4j7-r4q5-qw2c` - **Identifiers:** `GHSA-f4j7-r4q5-qw2c` · `CVE-2026-45829` · `PYSEC-2026-311` - **State:** Confirmed - **Severity:** CVSS 10.0 Critical - **Critical:** Yes: CVSS 9+, CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html) - **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md) · [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) - **Published:** 18 May 2026 - **Updated:** 5 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 18 May 2026, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 10.0: 9.0 or more. - CVSS score 10.0 (7.0 or more) and EPSS 0.15 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `chromadb` (PyPI): affected `>=1.0.0, <=1.5.9`; no fixed version yet ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The chromadb package, versions 1.0.0 through 1.5.9, has a pre-authentication code injection flaw. An unauthenticated attacker who can reach the server can send a malicious model repository with trust_remote_code set to true to the collections API endpoint, which lets them run arbitrary code on the server. The source lists no fixed version, so no fix is available yet; limiting network access to the ChromaDB server is the main protection until one is released. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 10.0 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`, from CNA (HiddenLayer) - **CISA KEV:** Not listed. - **EPSS:** 0.15, the 96th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:09 UTC: First seen by agentprime - 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f4j7-r4q5-qw2c) ## Sources - [GitHub Advisory Database: GHSA-f4j7-r4q5-qw2c](https://github.com/advisories/GHSA-f4j7-r4q5-qw2c) - [OSV: GHSA-f4j7-r4q5-qw2c](https://osv.dev/vulnerability/GHSA-f4j7-r4q5-qw2c) - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .