CVE-2026-130438 in Wiresharkinfo

Summary

by MITRE • 11/20/2026

Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability described involves multiple critical flaws within the packet dissection engines of Wireshark versions ranging from 4.4.0 through 4.4.19 and 4.6.0 through 4.6.9. These defects primarily manifest as denial-of-service conditions triggered by malformed or specially crafted network packets that cause the application to crash unexpectedly. The core issue lies in how specific protocol dissectors handle invalid data structures, buffer boundaries, or unexpected field values during the parsing process. When a user opens a capture file containing these maliciously constructed packets or views live traffic with such anomalies, the software fails to validate input sufficiently before attempting to interpret it as valid protocol data. This lack of robust error handling leads to memory corruption issues, typically in the form of out-of-bounds reads or writes, which subsequently cause segmentation faults and application termination.

From a technical perspective, these crashes are indicative of insufficient boundary checks within the parsing logic for various network protocols supported by Wireshark. Dissectors are responsible for breaking down raw packet data into human-readable fields based on protocol specifications. If a dissector assumes that certain fields exist or have specific lengths without verifying their presence against the actual packet size, it may attempt to access memory locations outside the allocated buffer. This behavior aligns with Common Weakness Enumeration categories such as CWE-125 Out-of-bounds Read and CWE-787 Out-of-bounds Write. The vulnerability is not limited to a single protocol but affects multiple dissectors, suggesting that the underlying framework or common parsing utilities used across different protocols may share similar defensive coding gaps. Attackers can exploit this by crafting packets with truncated headers, incorrect length fields, or malformed TLV structures that trigger these unchecked memory accesses during real-time capture analysis or offline file inspection.

The operational impact of this vulnerability is significant for security professionals and network administrators who rely on Wireshark as a primary tool for traffic analysis and incident response. A successful exploitation results in the immediate termination of the application, leading to data loss if unsaved work was present. More critically, it disrupts ongoing monitoring activities, potentially causing analysts to miss critical events during live captures. In scenarios where Wireshark is used within automated pipelines or integrated into larger security orchestration platforms, these crashes can cause service interruptions and degrade the reliability of threat detection systems. While the vulnerability primarily facilitates denial-of-service rather than remote code execution due to the nature of memory corruption in this context, it still poses a substantial risk to operational continuity and analyst productivity.

To mitigate these risks, users must upgrade Wireshark to version 4.6.10 or later for the 4.6 branch, or version 4.4.20 or later for the 4.4 branch, where patches have been applied to enforce stricter input validation within the affected dissectors. Until an update is feasible, analysts should exercise caution when opening capture files from untrusted sources and avoid viewing live traffic on networks known to contain potentially malicious payloads that might trigger these flaws. Additionally, employing sandboxed environments for analyzing suspicious captures can isolate potential crashes from the host system. This incident underscores the importance of rigorous input validation in network analysis tools and highlights the need for continuous security reviews of protocol parsing logic to prevent similar memory safety issues. The ATT&CK framework categorizes such exploitation under techniques related to resource exhaustion, specifically noting how application instability can be leveraged to disrupt availability.

Responsible

GitLab

Reservation

11/17/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00252

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!