dbcve.org
ChromadbApplication · Trychroma

CVE-2026-45832

HIGH · 8.8 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to after 1.5.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database to the authorization layer, allowing attackers to bypass authorization controls by using the V1 endpoints.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

All V1 collection-level endpoints in ChromaDB's Python project pass None for the tenant and database parameters to the authorization layer, allowing unauthorized access when the authorization layer cannot properly validate access due to missing context.

MitigationUpdate to the patched version of ChromaDB that correctly passes tenant and database parameters from V1 endpoints to the authorization layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromadbApplication
Affected:>= 0.5.0, <= 1.5.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed ChromaDB version
    Run 'pip show chromadb' or check your dependency lock file to identify the installed version number
    Affected if The installed version is between 0.5.0 and 1.5.9 inclusive
  2. Identify if V1 API endpoints are in use
    Review your API configuration or logs to determine if requests are being routed to V1 endpoints (typically /api/v1/ collection endpoints)
    Affected if V1 collection-level endpoints are exposed or accessible to clients
  3. Confirm authorization is enabled
    Inspect your ChromaDB configuration for authorization middleware or access control settings
    Affected if Authorization is configured but V1 endpoints bypass proper tenant/database context validation
  4. Verify tenant and database configuration in requests
    Examine API request logs or test collection-level operations to observe what tenant/database values are passed to the authorization layer
    Affected if Requests to V1 collection endpoints do not include explicit tenant/database parameters in the authorization context
  5. Check if V2 endpoints are available as alternative
    Review your API routing or proxy configuration to see if V2 endpoints (/api/v2/) are configured and accessible
    Affected if Only V1 endpoints are available and authorization cannot properly validate tenant/database identity

You are affected if your ChromaDB version is 0.5.0 through 1.5.9 AND V1 collection-level endpoints are accessible while authorization is enabled but fails to receive proper tenant/database context.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.5.9
Interim mitigation

Update to the patched version of ChromaDB that correctly passes tenant and database parameters from V1 endpoints to the authorization layer.

Recommended fix Moderate confidence

Latest stable release beyond version 1.5.9 (e.g., 1.6.0+ or current stable)

  1. 1. Identify all deployments running ChromaDB versions between 0.5.0 and 1.5.9 inclusive
  2. 2. Review your application's use of V1 collection-level API endpoints to understand authorization dependencies
  3. 3. Upgrade ChromaDB to the latest stable release that includes the fix for this authorization bypass vulnerability
  4. 4. After upgrading, verify that tenant and database parameters are properly passed to the authorization layer on V1 collection-level endpoints
  5. 5. Test that authorization controls function correctly after the upgrade, ensuring proper access restrictions on collection-level operations
  6. 6. Monitor for any breaking changes in authentication/authorization behavior post-upgrade
Caveat Review release notes for potential API or authorization behavior changes between affected versions and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chromadb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45832 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data