CVE-2026-130458 in Wireshark
Summary
by MITRE • 11/20/2026
IrDA 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 IrDA (Infrared Data Association) protocol dissector, specifically affecting Wireshark versions ranging from 4.4.0 through 4.4.19 and 4.6.0 through 4.6.9. This defect manifests as an application crash when processing malformed or specially crafted network packets that utilize the IrDA protocol stack. As a packet analysis tool, Wireshark is designed to parse raw network data into human-readable formats for security professionals and network administrators. The dissector acts as the parser responsible for interpreting specific protocol headers and payloads. In this instance, the logic governing the parsing of certain IrDA fields fails to adequately validate input boundaries or handle unexpected data structures, leading directly to a segmentation fault or similar memory corruption error that terminates the application process abruptly.
From a technical perspective, this issue represents a classic denial-of-service vector rooted in improper input validation and lack of robust exception handling during packet dissection. When an attacker transmits maliciously constructed packets containing invalid length fields, out-of-bounds offsets, or malformed header structures to a system running a vulnerable version of Wireshark, the dissector attempts to interpret these values without sufficient safeguards. This typically results in accessing memory locations that are not allocated for the current operation, triggering a crash. The vulnerability is particularly concerning because it can be triggered remotely if an attacker has access to the network segment where the victim machine is sniffing traffic, or locally if the user opens a captured packet file containing the malicious payload.
The operational impact of this vulnerability is primarily limited to availability due to its denial-of-service nature. A successful exploit causes Wireshark to crash unexpectedly, resulting in data loss for any ongoing capture sessions and requiring manual restart of the application. For security analysts relying on continuous monitoring or real-time packet inspection during incident response activities, such interruptions can hinder visibility into network events and delay threat detection efforts. While there is no indication that this vulnerability allows for arbitrary code execution or remote control of the host system, the potential for disrupting critical analysis workflows poses a significant risk to operational continuity in environments where Wireshark is used as part of an active defense strategy.
To mitigate this risk, organizations must ensure that all instances of Wireshark are updated to versions 4.6.10 or later and 4.4.20 or later, which contain the necessary patches for input validation within the IrDA dissector. Until upgrades can be performed, users should exercise caution when opening packet capture files from untrusted sources or avoid sniffing traffic on segments where malicious actors might inject crafted packets. Additionally, implementing network segmentation to limit exposure of analysis workstations to potentially hostile networks can reduce the attack surface. This vulnerability aligns with CWE-20 Improper Input Validation and is categorized under MITRE ATT&CK technique T1498 Network Denial of Service, highlighting its classification as an availability-focused exploit targeting software parsing logic rather than confidentiality or integrity mechanisms.