CVE-2025-6710VulnerabilityPublished 26 Jun 2025

CVE-2025-6710: MongoDB Server · Uncontrolled Recursion

Affects MongoDB ServerSource CVE Database V5

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

Data as of 26 Oct 2026, 06:26 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 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.5, 7.0.17, 6.0.21

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 26 Jun 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 2026-10-26.

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.5, 7.0.17 or 6.0.21.

Affected software

Product	Affected	Fixed in
MongoDB Inc MongoDB Server	Affected =6.0 =7.0 =8.0 <6.0.21 <7.0.17 <8.0.5	Fixed in 6.0.21 7.0.17 8.0.5

AI-suggested

European organizations should immediately assess their MongoDB Server deployments to identify affected versions (6.0 prior to 6.0.21, 7.0 prior to 7.0.17, and 8.0 prior to 8.0.5). If you cannot patch yet, organizations should implement network-level protections such as firewall rules to restrict access to MongoDB ports (default 27017) to trusted hosts only, minimizing exposure to untrusted networks. Deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with signatures or anomaly detection for unusual JSON payloads may help detect or block exploit attempts. For version 6.0 deployments, enforcing strong authentication and access controls reduces risk. Monitoring MongoDB server logs for crashes or unusual JSON parsing errors can provide early warning of exploitation attempts. Additionally, organizations should review and harden their MongoDB configurations, disabling unnecessary network exposure and enabling authentication and encryption where possible. Regular backups and tested recovery procedures are essential to mitigate impact from potential denial of service incidents. Finally, staying informed through MongoDB security advisories and threat intelligence feeds will help maintain timely defenses.

Description

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.

Impact

For European organizations relying on MongoDB Server for critical data storage and application backend services, this vulnerability presents a substantial risk of service disruption. Since the vulnerability can be exploited remotely without authentication on recent major versions (7.0 and 8.0), attackers could induce denial of service conditions, causing database crashes and downtime. This can lead to operational interruptions, loss of availability of business-critical applications, and potential cascading effects on dependent systems. Organizations in sectors such as finance, healthcare, telecommunications, and public services, which often deploy MongoDB for scalable data management, may face increased risk of service outages. Additionally, the requirement for authentication in version 6.0 reduces risk but does not eliminate it, especially in environments with weak access controls. Given the widespread adoption of MongoDB across Europe, the vulnerability could be exploited by threat actors aiming to disrupt services or as part of multi-stage attacks. The lack of known exploits in the wild currently reduces immediate risk, but the public disclosure and high severity score necessitate prompt remediation to prevent future exploitation. The vulnerability does not impact confidentiality or integrity directly but severely affects availability, which can have significant business impact.

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2025, 14:35 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats