CVE-2025-11626VulnerabilityPublished 10 Oct 2025Updated 27 Mar 2026

CVE-2025-11626: Wireshark · Infinite Loop

Affects WiresharkSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 10 Oct 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

Affected software

Product	Affected	Fixed in
Wireshark Foundation Wireshark	Affected =4.4.0 =4.2.0	Fixed in–

AI-suggested

To mitigate CVE-2025-11626, organizations should: 1) Avoid opening untrusted or unauthenticated capture files containing MONGO protocol traffic in affected Wireshark versions. 2) Restrict Wireshark usage to trusted personnel and environments to minimize exposure to crafted malicious traffic. 3) Monitor Wireshark vendor advisories and apply patches promptly once available. 4) Consider using alternative tools or updated Wireshark versions that have addressed this vulnerability. 5) Implement network segmentation and filtering to limit exposure of MONGO traffic to analysis workstations. 6) Educate analysts to recognize and report application hangs potentially caused by malformed packets. 7) Use sandboxing or containerization to isolate Wireshark processes, reducing impact of hangs on broader systems. These steps go beyond generic advice by focusing on operational controls and usage policies specific to this vulnerability's attack vector.

Description

MONGO dissector infinite loop in Wireshark 4.4.0 to 4.4.9 and 4.2.0 to 4.2.13 allows denial of service

Impact

The primary impact of CVE-2025-11626 is denial of service against Wireshark users. Organizations relying on Wireshark for network troubleshooting, forensic analysis, or security monitoring may experience application hangs or crashes when processing malicious MONGO traffic or capture files. This can delay detection and response to network incidents, reduce analyst productivity, and potentially obscure ongoing attacks. Since Wireshark is widely used in enterprise, government, and academic environments, the disruption could affect critical network operations and security workflows. However, the vulnerability does not allow code execution, data leakage, or privilege escalation, limiting its impact to availability. The requirement for user interaction and local access reduces the risk of remote exploitation but does not eliminate it, especially in environments where untrusted capture files are shared or imported. Overall, the vulnerability could be leveraged by attackers to cause targeted disruption in network analysis environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:20 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats