dbcve.org
MongoDBDatabase / datastore

CVE-2026-8201

HIGH · 8.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 7.0.34 / 8.0.23 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
A use-after-free vulnerability exists in MongoDB's Field-Level Encryption (FLE) query analysis component, affecting client-side uses of mongocryptd and crypt_shared. Triggering this vulnerability requires control over the structure of a client's FLE-related query. This issue impacts MongoDB Server’s mongocryptd component v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.

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 · high confidence

A use-after-free vulnerability exists in MongoDB's Field-Level Encryption (FLE) query analysis component, specifically in the mongocryptd and crypt_shared client-side libraries. An attacker with control over the structure of FLE-related queries can trigger this memory safety issue.

MitigationUpgrade MongoDB Server to version 7.0.34, 8.0.23, 8.2.9, or 8.3.2 (or later) as appropriate for the deployment to patch the vulnerable mongocryptd component.

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
MongoDBDatabase / datastore
Affected:>= 7.0.0, < 7.0.34>= 8.0.0, < 8.0.23>= 8.2.0, < 8.2.9>= 8.3.0, < 8.3.2

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. Identify MongoDB Server version
    Run 'db.version()' in the mongo shell or 'mongod --version' to retrieve the installed server version
    Affected if The version falls within any of these ranges: 7.0.0-7.0.33, 8.0.0-8.0.22, 8.2.0-8.2.8, or 8.3.0-8.3.1
  2. Verify if Field-Level Encryption is enabled
    Check the MongoDB configuration (mongod.conf) for 'encryption' settings, or query the cluster configuration for FLE-related options using 'db.adminCommand({getParameter: 1, enableEncryption: 1})'
    Affected if Field-Level Encryption is enabled and the server version is vulnerable as identified in step 1
  3. Confirm mongocryptd process presence
    Check for a running mongocryptd process on the system using 'ps aux | grep mongocryptd' or review the MongoDB deployment architecture for FLE query analysis components
    Affected if mongocryptd is running and the server version is in a vulnerable range
  4. Check crypt_shared library version
    Locate and inspect the crypt_shared library version if deployed separately from the main MongoDB binaries, typically found in the MongoDB bin directory
    Affected if The crypt_shared library version matches the vulnerable server versions and FLE is in use

You are affected if your MongoDB server version is below 7.0.34, 8.0.23, 8.2.9, or 8.3.2 AND Field-Level Encryption is enabled or mongocryptd is in use.

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 7.0.34 / 8.0.23 / 8.2.9 or later
Fixed in 7.0.348.0.238.2.9
Interim mitigation

Upgrade MongoDB Server to version 7.0.34, 8.0.23, 8.2.9, or 8.3.2 (or later) as appropriate for the deployment to patch the vulnerable mongocryptd component.

Recommended fix High confidence

Upgrade to MongoDB Server 7.0.34, 8.0.23, 8.2.9, or 8.3.2 (or later) depending on your current major version branch

  1. 1. Identify the current MongoDB Server version by running: db.version() in the mongo shell or checking the installed package version
  2. 2. Determine which major version branch you are on (7.0.x, 8.0.x, 8.2.x, or 8.3.x)
  3. 3. Stop the MongoDB Server service using the appropriate command for your system (e.g., systemctl stop mongod or service mongod stop)
  4. 4. For RHEL/CentOS/Fedora: Run sudo yum install -y mongodb-org-server to upgrade to the latest available version in your repository, then verify the version is >= the fixed version for your branch
  5. 5. For Debian/Ubuntu: Run sudo apt-get update && sudo apt-get install -y mongodb-org-server to upgrade, then verify the version is >= the fixed version for your branch
  6. 6. For macOS (via Homebrew): Run brew services stop mongodb-community && brew upgrade mongodb-community && brew services start mongodb-community
  7. 7. Restart the MongoDB service: systemctl start mongod or service mongod start
  8. 8. Verify the upgrade was successful by running db.version() and confirming it shows 7.0.34, 8.0.23, 8.2.9, or 8.3.2 or higher
Caveat Minor releases typically include backward-compatible changes; however, always review the release notes for any behavior changes before upgrading production systems

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8201 — 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-8201 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