CVE-2026-130451 in Wireshark
Summary
by MITRE • 11/20/2026
Multiple protocol dissector infinite loops in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified involves multiple protocol dissectors within the Wireshark software suite, specifically affecting versions ranging from 4.4.0 through 4.4.19 and 4.6.0 through 4.6.9. This flaw is characterized by an infinite loop condition that occurs during the parsing of network packet data for specific protocols. When a dissector encounters malformed or specially crafted input, it fails to properly advance its internal state machine or pointer position within the buffer. Instead of detecting the invalid structure and terminating the parse operation with an error code, the logic enters a repetitive cycle that consumes available processing resources indefinitely. This behavior is particularly dangerous in automated analysis environments where large volumes of traffic are processed continuously without manual intervention for each packet stream.
From a technical perspective, this issue represents a classic failure in input validation and state management within protocol parsers. Dissectors rely on strict adherence to protocol specifications to determine the length and structure of subsequent data fields. When an attacker provides packets with incorrect field lengths or unexpected byte sequences that do not match expected patterns, the dissector may attempt to read beyond valid boundaries or re-evaluate a segment repeatedly without making progress. This lack of bounds checking and loop termination conditions leads directly to resource exhaustion on the host system running Wireshark. The operating system scheduler will continue to allocate CPU time to this process until it is manually terminated or the system becomes unresponsive due to high load, effectively achieving a denial of service against the application and potentially impacting other processes sharing those resources.
The operational impact of this vulnerability extends beyond simple application freezing. In professional security operations centers or network monitoring environments where Wireshark is used for real-time traffic analysis, such an infinite loop can disrupt critical workflows. Analysts may lose access to live capture data, leading to gaps in visibility during incident response activities. Furthermore, if the software is integrated into larger automation pipelines that process packet captures programmatically, these loops can cause pipeline failures, delayed reporting, and increased latency across dependent systems. The severity is heightened by the fact that network protocols are ubiquitous; an attacker does not need direct access to the victim machine but only needs to be able to inject crafted packets into a monitored segment or provide malicious capture files for analysis, making this a remotely exploitable threat vector in many deployment scenarios.
This vulnerability aligns with Common Weakness Enumeration (CWE) category CWE-835, which describes loops that do not terminate correctly due to missing loop termination conditions. It also relates closely to CWE-20, Improper Input Validation, as the root cause is the failure to validate packet structures before processing them through complex parsing logic. In terms of attack tactics, this behavior corresponds to MITRE ATT&CK technique T1499, Endpoint Denial of Service, where an adversary aims to degrade or deny availability of target resources by exhausting system capacity. The exploitation does not require privilege escalation or code execution but relies purely on resource consumption through logical flaws in the parsing engine.
Mitigation strategies primarily involve updating the Wireshark installation to a version that includes patches for these specific dissector issues, as newer releases have implemented stricter validation checks and loop safeguards. Organizations should ensure their network analysis tools are maintained with the latest security updates provided by the vendor. Additionally, when processing untrusted or potentially malicious capture files, it is advisable to use sandboxed environments or virtual machines isolated from critical infrastructure to contain any potential resource exhaustion events. Implementing input filtering at the network ingress point can also reduce exposure by preventing malformed packets from reaching analysis tools in real-time scenarios. Regular auditing of dissector configurations and staying informed about vendor advisories are essential practices for maintaining resilience against such logic-based denial of service attacks.