CVE-2026-130447 in Wireshark
Summary
by MITRE • 11/20/2026
Exported PDU protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified involves a critical flaw within the exported Protocol Data Unit (PDU) protocol dissector, specifically affecting Wireshark versions ranging from 4.4.0 through 4.4.19 and 4.6.0 through 4.6.9. This security issue manifests as an application crash when processing malformed or specially crafted network traffic that utilizes the exported PDU protocol structure. The dissector, which is responsible for parsing and interpreting packet data to provide human-readable insights into network communications, fails to adequately validate input parameters before attempting memory operations. This lack of robust boundary checking allows attackers to trigger a denial of service condition by causing the application to terminate unexpectedly during the analysis phase.
From a technical perspective, this flaw aligns with CWE-125, Out-of-bounds Read, or potentially CWE-400, Uncontrolled Resource Consumption, depending on the specific memory access pattern that leads to the crash. The dissector likely attempts to read data from an invalid memory address or processes a buffer without verifying its length against expected limits defined by the protocol specification. When such malformed packets are encountered, either through direct capture analysis or when opening captured packet files containing this malicious payload, the application encounters an unrecoverable error state. This results in immediate termination of the Wireshark process, effectively denying service to the analyst who relies on the tool for network troubleshooting and security monitoring.
The operational impact of this vulnerability is primarily focused on availability rather than confidentiality or integrity. For professionals using Wireshark as a primary diagnostic tool, encountering such crashes can lead to significant workflow interruptions and potential loss of unsaved work if automatic recovery mechanisms are not enabled or fail due to the severity of the memory fault. In environments where automated packet analysis tools rely on stable parsing engines, this vulnerability could disrupt continuous monitoring systems that ingest network traffic for real-time threat detection. While the risk of remote code execution is generally lower in dissectors unless specific heap corruption techniques are employed, the certainty of a crash makes it a high-priority issue for stability and reliability assurance within security analysis workflows.
Mitigation strategies involve upgrading to patched versions of Wireshark where this input validation logic has been corrected. Developers have implemented stricter checks to ensure that all memory accesses remain within valid bounds defined by the protocol structure. Until an upgrade is feasible, users should exercise caution when opening packet capture files from untrusted sources or analyzing traffic from potentially hostile networks using affected versions. Enabling crash recovery features and regularly saving work can mitigate data loss risks associated with unexpected terminations. Furthermore, organizations deploying automated analysis tools based on Wireshark libraries should ensure their dependencies are updated to exclude vulnerable dissector implementations, thereby maintaining the integrity of network visibility infrastructure against denial-of-service attacks targeting analytical software.