CVE-2025-11626 | Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark

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

Published: 2025-10-10 Last update: 2025-12-03 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-11626 is rated Low Risk (22.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-11626

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-10-11 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-11626

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-11626

OS Trackers for CVE-2025-11626

vendor priority summary link
alpine — CVE-2025-11626: 1 source package rows (wireshark); 14 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 14. https://security.alpinelinux.org/vuln/CVE-2025-11626
debian not yet assigned CVE-2025-11626 not yet assigned priority: Debian including 1 source packages (wireshark), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-11626
redhat medium — https://access.redhat.com/security/cve/CVE-2025-11626
suse medium CVE-2025-11626 severity moderate: SUSE including 38 source package names (2.2.1-5.14:libxml2-2-2.11.6-slfo.1.1_6.1, 2.2.1-5.27:libxml2-2-2.11.6-slfo.1.1_6.1, …), 215 product×package rows across 76 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (76 product lines)): Fixed 187, Known Not Affected 22, First Fixed 6. https://www.suse.com/security/cve/CVE-2025-11626/
ubuntu medium CVE-2025-11626 medium priority: Ubuntu including 1 source packages (wireshark), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 1. https://ubuntu.com/security/CVE-2025-11626

Affected software / configurations for CVE-2025-11626

Vendor Product Version Raw CPE
wireshark wireshark >= 4.2.0, < 4.2.14 cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*
wireshark wireshark >= 4.4.0, < 4.4.10 cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*

References for CVE-2025-11626

cvelogic Threat Intelligence