VulnerabilityPublished 7 Jul 2025

CVE-2025-6714: MongoDB Server · Excessive Iteration

Affects MongoDB ServerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 8.0.9 : patch MongoDB Server soon.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.9, 7.0.20, 6.0.23

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade MongoDB Server to 8.0.9, 7.0.20 or 6.0.23.

Affected software

Product	Affected	Fixed in
MongoDB Inc MongoDB Server	Affected =6.0 =7.0 =8.0 <6.0.23 <7.0.20 <8.0.9	Fixed in 6.0.23 7.0.20 8.0.9

AI-suggested

To mitigate this vulnerability, European organizations should prioritize upgrading MongoDB Server to the fixed versions: 6.0.23 or later, 7.0.20 or later, and 8.0.9 or later. Immediate patching is the most effective measure. In parallel, organizations should review and harden their HAProxy load balancer configurations to implement strict input validation and connection timeouts to limit the impact of malformed or incomplete data packets. Network segmentation and firewall rules should restrict access to mongos instances, allowing only trusted sources to connect. Monitoring and alerting on mongos responsiveness and resource consumption can provide early detection of exploitation attempts. Additionally, implementing rate limiting and connection throttling on HAProxy can reduce the risk of resource exhaustion. Organizations should also conduct thorough testing of their sharded cluster environments post-patching to ensure stability and resilience. Finally, maintaining an incident response plan that includes database service recovery procedures will help minimize downtime if exploitation occurs before patching.

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.

Impact

For European organizations, this vulnerability poses a significant risk to the availability of MongoDB sharded clusters, particularly those using HAProxy load balancers. MongoDB is widely used across various sectors including finance, healthcare, telecommunications, and government services in Europe. An unresponsive mongos component can halt database query routing, leading to service outages, degraded application performance, and potential operational disruptions. Organizations with critical real-time data processing or high-availability requirements may face severe business continuity challenges. The impact is amplified in sectors where data availability is crucial for compliance and operational integrity, such as banking and healthcare. Additionally, prolonged downtime could lead to reputational damage and financial losses. Since exploitation requires no authentication and can be triggered remotely, threat actors could leverage this vulnerability to launch denial-of-service attacks against European enterprises' backend infrastructure, especially those exposed to the internet or insufficiently segmented networks.

CWE-834Excessive Iteration (opens in a new tab)
Class weakness
The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jira.mongodb.org/browse/SERVER-106753 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 15:14 UTC

WeaknessesCWE-834, CWE-400

Technical details

References

Community reviews

Related threats