MongoDB Server: Uncontrolled Resource Consumption
CVE-2025-6714 is a high-severity uncontrolled resource consumption vulnerability in MongoDB Server from MongoDB, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 6.0.23, 7.0.20, 8.0.9 as the first without the flaw, so updating MongoDB Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update MongoDB Server to 6.0.23 or 7.0.20 or 8.0.9, whichever matches your release line, or a later version.
- Update Mongodb to 6.0.23 or 7.0.20 or 8.0.9, whichever matches your release line, or a later version.
- Read the advisory on jira.mongodb.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MongoDB | MongoDB Server | 6.0 up to, but not including, 6.0.23; 7.0 up to, but not including, 7.0.20; 8.0 up to, but not including, 8.0.9 | 6.0.23, 7.0.20, 8.0.9 |
| MongoDB | Mongodb | 6.0.0 up to, but not including, 6.0.23; 7.0.0 up to, but not including, 7.0.20; 8.0.0 up to, but not including, 8.0.9 | 6.0.23, 7.0.20, 8.0.9 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (mongodb.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How developers prevent this class of flaw
- Ensure that protocols have specific limits of scale placed on them.
- Ensure that all failures in resource allocation place the system into a safe posture.
More Uncontrolled Resource Consumption vulnerabilities (CWE-400)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- jira.mongodb.org/browse/SERVER-106753Issue Tracking
Other vulnerabilities in MongoDB Server
- 7.5 High severity
- 8.8 High severity
- 7.1 High severity
- 10.0 Critical severity
- 8.4 High severity
- 7.2 High severity
Recent Uncontrolled Resource Consumption vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 8.2 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.