Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

ChromaDB Python project has a pre-authentication code injection vulnerability

CVE-2026-45829GHSA-f4j7-r4q5-qw2c

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI chromadb

    Affected
    >= 1.0.0, <= 1.5.9
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · 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/E:P · score source
EPSS
  • CVE-2026-45829: 15.15% estimated exploitation activity in the next 30 days; percentile 96.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A pre-authentication, code injection vulnerability in version 1.0.0 or later of the ChromaDB Python project allows an unauthenticated attacker to run arbitrary code on the server by sending a malicious model repository and trustremotecode set to true in the /api/v2/tenants/{tenant}/databases/{db}/collections endpoint.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-f4j7-r4q5-qw2c

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-f4j7-r4q5-qw2c

  4. Revision 1 · created ·

    Published from ghsa record GHSA-f4j7-r4q5-qw2c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45829

Advisory: ChromaDB Python project has a pre-authentication code injection vulnerability
IDs: CVE-2026-45829, GHSA-f4j7-r4q5-qw2c
Record: https://patchnext.com/advisories/cve-2026-45829 (revision 4, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI chromadb: affected >= 1.0.0, <= 1.5.9

## Suggested inspection (read-only)
- `python -m pip show chromadb`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on chromadb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f4j7-r4q5-qw2c (GitHub-reviewed advisory GHSA-f4j7-r4q5-qw2c lists affected ranges: PyPI chromadb >=1.0.0 <=1.5.9)
- Verified: https://osv.dev/vulnerability/GHSA-f4j7-r4q5-qw2c (OSV record GHSA-f4j7-r4q5-qw2c lists affected ranges: PyPI chromadb >=1.0.0 <=1.5.9)

Commands are suggestions: review each one before running it.

Loading voting…