dbcve.org
MongoDBDatabase / datastore

CVE-2025-6710

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
MongoDB Server may be susceptible to stack overflow due to JSON parsing mechanism, where specifically crafted JSON inputs may induce unwarranted levels of recursion, resulting in excessive stack space consumption. Such inputs can lead to a stack overflow that causes the server to crash which could occur pre-authorisation. This issue affects MongoDB Server v7.0 versions prior to 7.0.17 and MongoDB Server v8.0 versions prior to 8.0.5. The same issue affects MongoDB Server v6.0 versions prior to 6.0.21, but an attacker can only induce denial of service after authenticating.

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

Stack overflow vulnerability in MongoDB Server's JSON parsing mechanism where specially crafted JSON inputs cause excessive recursion, leading to stack space exhaustion and server crash. This is a pre-authentication denial-of-service vulnerability affecting versions 7.0.x before 7.0.17 and 8.0.x before 8.0.5.

MitigationUpgrade MongoDB Server to version 7.0.17, 8.0.5, or 6.0.21 or later to patch the recursive JSON parsing issue.

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.5

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installed MongoDB version
    Run 'db.version()' in the mongo shell, or use 'mongod --version' from command line, or check the package manager for the installed mongodb-server package version
    Affected if The installed version is >= 6.0.0 and < 6.0.21, OR >= 7.0.0 and < 7.0.17, OR >= 8.0.0 and < 8.0.5
  2. Confirm the server is running and accessible
    Verify the mongod process is running (ps aux | grep mongod) and the port 27017 is listening (netstat -tlnp | grep 27017)
    Affected if The server is running and exposed on a network port (pre-authentication means the vulnerability can be triggered before any authentication occurs)
  3. Determine if JSON parsing features are in use
    Review application code or configuration for JSON input handling via MongoDB queries, aggregation pipelines using $jsonSchema, or any custom JSON parsing through mongosh or client drivers
    Affected if Applications or scripts send JSON data to MongoDB that could trigger the recursive parsing vulnerability

You are affected if your MongoDB version falls within any of the vulnerable ranges (6.0.0-6.0.20, 7.0.0-7.0.16, or 8.0.0-8.0.4) and the server accepts JSON input, since the stack overflow occurs during JSON parsing before any authentication takes place.

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.5 or later
Fixed in 6.0.217.0.178.0.5
Interim mitigation

Upgrade MongoDB Server to version 7.0.17, 8.0.5, or 6.0.21 or later to patch the recursive JSON parsing issue.

Recommended fix High confidence

6.0.21 (or later for 6.0.x), 7.0.17 (or later for 7.0.x), 8.0.5 (or later for 8.0.x)

  1. Schedule a maintenance window and create a full backup of the MongoDB database
  2. Stop the MongoDB server or cluster
  3. For MongoDB 6.0.x: Upgrade to version 6.0.21 or later
  4. For MongoDB 7.0.x: Upgrade to version 7.0.17 or later
  5. For MongoDB 8.0.x: Upgrade to version 8.0.5 or later
  6. After upgrading, restart the MongoDB server
  7. Verify the server starts successfully and responds to queries
  8. Test application functionality to ensure compatibility with the upgraded version
Caveat Standard MongoDB upgrade precautions apply; review release notes for any behavior changes between minor versions

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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