UTC

chromadb

4 published advisories.

Registry
PyPI
Advisories
4
Latest fix
No fix yet
Exploited in the wild
None listed
Advisories with no fix yet

4 advisories have no fixed release in any version yet. What can be done meanwhile:

General guidance from ShieldPi, not a vendor fix

  • Command or code injection. Remove or disable the affected server or tool, or run it in a sandbox with no secrets in its environment.GHSA-36p7-vc44-83pf · GHSA-f4j7-r4q5-qw2c
  • Unsafe deserialization. Do not let it load files, models or data from sources you do not trust, and keep its RPC and socket ports reachable only from localhost or hosts you trust.GHSA-f4j7-r4q5-qw2c

Check your projects

shieldpi agent-config checks agent and MCP packages from npm and PyPI, not chromadb. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.

osv-scanner scan source -r .

Or check a lockfile against ShieldMap in your browser.

Provenance

Source: github.com/chroma-core/chroma, named in the package metadata (not verified)

0 of the last 10 releases of chromadb were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.

  • 1.5.9
  • 1.5.8
  • 1.5.7
  • 1.5.6
  • 1.5.5
  • 1.5.4
  • 1.5.3
  • 1.5.2
  • 1.5.1
  • 1.5.0

Green: published with provenance. Grey: without.

OpenSSF Scorecard: 5.3 of 10 on 2026-11-16.

No dangerous CI workflows
10/10
CI tokens read-only by default
0/10
Build dependencies pinned
0/10
Branch protection
Not checked
Changes reviewed before merge
8/10
Signed releases
0/10
Actively maintained
10/10
Security policy
0/10
Full Scorecard →

Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.

Advisories
AdvisorySeverityAffectedFixed inPublished
ChromaDB allows any authenticated users to arbitrarily read, write, update, or delete data in any tenant's collectionCVE-2026-45830High>= 0.4.17, <= 1.5.9No fix yet2026-06-12
ChromaDB has a code injection vulnerabilityCVE-2026-45833Critical>= 0.4.17, <= 1.5.9No fix yet2026-06-12
ChromaDB's SimpleRBACAuthorizationProvider doesn't check which tenant, database, or collection a permission applies toCVE-2026-45831High>= 0.5.0, <= 1.5.9No fix yet2026-06-12
ChromaDB Python project has a pre-authentication code injection vulnerabilityCVE-2026-45829Critical>= 1.0.0, <= 1.5.9No fix yet2026-05-18

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].