dbcve.org
MongoDBDatabase / datastore

CVE-2026-11933

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

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 Server's server-side JavaScript engine when converting BSON documents to JavaScript arrays. An authenticated user with read privileges who is able to run server-side JavaScript (for example, via $where or $function) can cause the server to access memory that has already been freed. This may result in disclosure of information from the mongod process memory or a denial of service through a server crash.

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
How this class of weakness works · CWE-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 4.4.0, < 4.4.31>= 5.0.0, < 5.0.34>= 6.0.0, < 6.0.29>= 7.0.0, < 7.0.37>= 8.0.0, < 8.0.26>= 8.2.0, < 8.2.11>= 8.3.0, < 8.3.4

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

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 4.4.31 / 5.0.34 / 6.0.29 or later
Fixed in 4.4.315.0.346.0.29
Vendor patch jira.mongodb.org →
Recommended fix High confidence

Upgrade to one of the following fixed releases: MongoDB 4.4.31, 5.0.34, 6.0.29, or 7.0.37 (choose the release matching your current major version branch)

  1. 1. Identify the currently running MongoDB version using: db.version() or mongod --version
  2. 2. Determine which release branch your current version belongs to (4.4.x, 5.0.x, 6.0.x, or 7.0.x)
  3. 3. For MongoDB Community Server: Download the appropriate fixed version from https://www.mongodb.com/try/download/community
  4. 4. For MongoDB Enterprise: Download from https://www.mongodb.com/try/download/enterprise
  5. 5. Before upgrading, backup all databases using mongodump or fsyncLock/fsyncUnlock
  6. 6. For rolling upgrades within the same major version (e.g., 6.0.x to 6.0.29), follow MongoDB's rolling upgrade documentation
  7. 7. For major version upgrades (e.g., 6.0.x to 7.0.x), review the upgrade guide at https://www.mongodb.com/docs/manual/release-notes/
  8. 8. After upgrade, verify the server starts successfully and test application functionality

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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