dbcve.org
MongoDBDatabase / datastore

CVE-2025-6714

HIGH · 7.5 CVSS v3.1 Published 2025-07-07
Fix available
A fix is available. Upgrade to 6.0.23 / 7.0.20 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's mongos component can become unresponsive to new connections due to incorrect handling of incomplete data. This affects MongoDB when configured with load balancer support. This issue affects MongoDB Server v6.0 prior to 6.0.23, MongoDB Server v7.0 prior to 7.0.20 and MongoDB Server v8.0 prior to 8.0.9 Required Configuration: This affects MongoDB sharded clusters when configured with load balancer support for mongos using HAProxy on specified ports.

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

The mongos component in MongoDB sharded clusters becomes unresponsive to new connections when configured with load balancer support (HAProxy). This occurs due to incorrect handling of incomplete data, causing a denial-of-service condition where the router cannot accept additional client connections.

MitigationUpgrade MongoDB Server to version 6.0.23, 7.0.20, or 8.0.9 or later. For immediate workarounds, consider bypassing HAProxy temporarily or implementing stricter connection timeouts, though upgrading is the definitive fix.

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.23>= 7.0.0, < 7.0.20>= 8.0.0, < 8.0.9

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. Confirm MongoDB deployment is a sharded cluster
    Check if mongos (mongos daemon) is running in your environment. Run 'ps aux | grep mongos' or check your MongoDB architecture documentation to verify you are using mongos routers.
    Affected if Your deployment uses mongos routers for sharded cluster configuration
  2. Identify MongoDB server version
    Connect to mongos with mongosh and run 'db.version()' or run 'mongod --version' on the server. Compare the version against the affected ranges: 6.0.0-6.0.22, 7.0.0-7.0.19, 8.0.0-8.0.8.
    Affected if The installed version falls within any of the affected version ranges
  3. Verify load balancer (HAProxy) is in use
    Check your infrastructure configuration for HAProxy or any load balancer sitting in front of mongos routers. Review your network topology or HAProxy configuration files.
    Affected if HAProxy or a load balancer is configured to route traffic to mongos instances

You are affected if you run a sharded cluster with mongos behind HAProxy and your MongoDB version is 6.0.0-6.0.22, 7.0.0-7.0.19, or 8.0.0-8.0.8.

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.23 / 7.0.20 / 8.0.9 or later
Fixed in 6.0.237.0.208.0.9
Interim mitigation

Upgrade MongoDB Server to version 6.0.23, 7.0.20, or 8.0.9 or later. For immediate workarounds, consider bypassing HAProxy temporarily or implementing stricter connection timeouts, though upgrading is the definitive fix.

Recommended fix High confidence

MongoDB Server 6.0.23, 7.0.20, or 8.0.9 (depending on your current major version)

  1. 1. Schedule a maintenance window for the upgrade
  2. 2. Ensure you have a complete backup of your MongoDB cluster before proceeding
  3. 3. For sharded clusters with load balancer support, upgrade the mongos instances first: For v8.0.x upgrade to 8.0.9, for v7.0.x upgrade to 7.0.20, for v6.0.x upgrade to 6.0.23
  4. 4. Follow MongoDB's recommended upgrade path (upgrade through sequential minor versions if jumping multiple minor releases)
  5. 5. After upgrading mongos, restart the load balancer/HAProxy to ensure clean connections
  6. 6. Verify mongos is responsive to new connections by testing client connections through the load balancer
  7. 7. Monitor system logs for any errors or resource consumption issues
Caveat Standard MongoDB minor version upgrade risks apply - review release notes for any behavior changes between your current version and the target fixed version

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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