MongoDBDatabase / datastore
CVE-2026-13072
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 · uneditedWhen compute mode is enabled on a standalone mongod instance, insufficient validation of externally sourced BSON data during aggregation pipeline processing can result in memory corruption, potentially leading to process termination or other unintended behavior. This configuration is non-default and requires explicit enablement at startup.
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 confidenceWhen compute mode is explicitly enabled on a standalone mongod instance, the aggregation pipeline processor does not properly validate externally sourced BSON data, leading to memory corruption. This can cause process termination or unpredictable behavior.
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
>= 7.0.0, < 7.0.39>= 8.0.0, < 8.0.28>= 8.2.0, < 8.2.12>= 8.3.0, < 8.3.7CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MongoDB installation and versionRun 'db.version()' in mongosh or 'mongod --version' from command line to identify the installed MongoDB versionAffected if Cannot determine version or MongoDB is not installed
-
Verify standalone topologyExecute 'rs.status()' in mongosh - if it returns 'not running with --replSet' the instance is standalone; alternatively check 'db.adminCommand({isMaster: 1}).msg' returns 'isdbgrid' for sharded clustersAffected if Instance is a replica set member or sharded cluster (vulnerability applies only to standalone instances)
-
Check if compute mode is enabledRun 'db.adminCommand({getParameter: 1, computeMode: 1})' or inspect mongod configuration file for 'computeMode' settingAffected if Compute mode returns a value other than 'disabled' or is set in configuration - this is the critical enabler for the vulnerability
A user is affected only if they have a standalone (non-replica set, non-sharded) MongoDB instance with compute mode explicitly enabled, running any version where the BSON validation weakness exists in aggregation pipelines.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data7.0.398.0.288.2.12
Disable compute mode unless operationally critical, and apply MongoDB patches when available. Evaluate whether compute mode is required for your workload.
Fix this in MongoDB
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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