dbcve.org
MongoDBDatabase / datastore

CVE-2025-6706

HIGH · 8.8 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to 6.0.21 / 7.0.17 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
An authenticated user may trigger a use after free that may result in MongoDB Server crash and other unexpected behavior, even if the user does not have authorization to shut down a server. The crash is triggered on affected versions by issuing an aggregation framework operation using a specific combination of rarely-used aggregation pipeline expressions. This issue affects MongoDB Server v6.0 version prior to 6.0.21, MongoDB Server v7.0 version prior to 7.0.17 and MongoDB Server v8.0 version prior to 8.0.4 when the SBE engine is enabled.

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

An authenticated user can trigger a use-after-free vulnerability in MongoDB Server's aggregation framework by using a specific combination of rarely-used pipeline expressions when the SBE (Slot-Based Execution) engine is enabled. This causes memory corruption leading to server crash, even for users lacking shutdown authorization.

MitigationUpgrade MongoDB Server to version 6.0.21+, 7.0.17+, or 8.0.4+ to patch the vulnerability. If immediate upgrade is not feasible, consider disabling the SBE engine as a workaround if the environment permits.

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:>= 6.0.0, < 6.0.21>= 7.0.0, < 7.0.17>= 8.0.0, < 8.0.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

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 MongoDB Server version
    Run db.version() in the mongo shell or use mongod --version from command line
    Affected if Version is 6.0.0-6.0.20, 7.0.0-7.0.16, or 8.0.0-8.0.3 (falls within unpatched ranges)
  2. Verify if SBE engine is enabled
    Run db.adminCommand({getParameter: 1, featureFlagSBE: 1}) in the mongo shell to check the SBE feature flag status
    Affected if featureFlagSBE returns true or is enabled - the vulnerability only triggers when SBE is active
  3. Confirm authentication is in use
    Check server authentication status via db.adminCommand({connectionStatus: 1}) or review auth settings in mongod.conf
    Affected if The server accepts authenticated connections - the attacker needs valid credentials to trigger the flaw

User is affected if MongoDB version is in the vulnerable range AND the SBE engine is enabled AND the server accepts authenticated user connections.

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 6.0.21 / 7.0.17 / 8.0.4 or later
Fixed in 6.0.217.0.178.0.4
Interim mitigation

Upgrade MongoDB Server to version 6.0.21+, 7.0.17+, or 8.0.4+ to patch the vulnerability. If immediate upgrade is not feasible, consider disabling the SBE engine as a workaround if the environment permits.

Recommended fix High confidence

Upgrade to 6.0.21 (or later 6.0.x) if on v6.0.x; 7.0.17 (or later 7.0.x) if on v7.0.x; 8.0.4 (or later 8.0.x) if on v8.0.x

  1. 1. Identify current MongoDB version by running: db.version() or mongod --version
  2. 2. Based on your current major version, plan upgrade to the minimum fixed release: 6.0.21 for v6.0.x, 7.0.17 for v7.0.x, or 8.0.4 for v8.0.x
  3. 3. Perform a full backup of all databases before upgrading
  4. 4. Test the upgrade in a non-production environment first
  5. 5. For replica sets, perform rolling upgrade following MongoDB documentation (upgrade secondary members first, then primary)
  6. 6. For sharded clusters, upgrade config servers first, then shards, then mongos routers
  7. 7. After upgrade, verify the server starts successfully and all data is accessible
  8. 8. Confirm the fixed version is running: db.version()
Caveat Cross-major-version upgrades (e.g., 6.0→7.0 or 7.0→8.0) may have breaking changes; review MongoDB release notes for compatibility considerations before upgrading

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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