CVE-2026-130461 in Wireshark
Summary
by MITRE • 11/20/2026
IEEE 1609.2 protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified within the IEEE 1609.2 protocol dissector affects specific versions of network analysis software, specifically ranging from version 4.6.0 through 4.6.9 and from 4.4.0 through 4.4.19. This flaw is categorized as a denial of service vulnerability resulting in application crash due to improper input validation or handling within the parsing logic for IEEE 1609.2 data structures. The IEEE 1609.2 standard defines security services for Wireless Access in Vehicular Environments, commonly known as WAVE or DSRC, which are critical for secure vehicle-to-everything communication. When a network analyst or automated system processes malformed or specially crafted packets that adhere to the general structure of IEEE 1609.2 but contain invalid fields or unexpected data lengths, the dissector fails to handle these anomalies gracefully. Instead of discarding the packet and continuing operation, the software encounters an unrecoverable error state, leading to a segmentation fault or similar crash condition that terminates the application process immediately.
From a technical perspective, this issue aligns with CWE-20 Improper Input Validation and potentially CWE-416 Use After Free if memory management errors are involved in the parsing routine. The root cause typically lies in the assumption that incoming data will strictly conform to expected boundaries or types without sufficient bounds checking during the deserialization of cryptographic headers, certificates, or signatures embedded within the IEEE 1609.2 frames. An attacker who can inject malicious traffic into a network segment being monitored by this tool can exploit this weakness remotely if the software is configured to automatically decode such protocols upon packet arrival. The operational impact is significant for security professionals and incident responders who rely on continuous availability of their analysis tools during active investigations or real-time monitoring scenarios. A crash in the dissector not only disrupts the immediate session but may also lead to data loss regarding captured packets that were being processed at the time of failure, thereby hindering forensic reconstruction efforts.
This vulnerability maps directly to MITRE ATT&CK technique T1498 Network Denial of Service, specifically under sub-techniques involving resource exhaustion or application crash via malformed input. While it does not typically allow for remote code execution in this specific manifestation, the reliability impact on critical security infrastructure is substantial. Organizations deploying these versions of network analysis software must recognize that exposure to untrusted networks where IEEE 1609.2 traffic might be present poses a direct risk to operational continuity. Mitigation strategies primarily involve upgrading to patched versions of the software where developers have implemented robust input validation, boundary checks, and exception handling within the protocol dissector logic. Until an upgrade is feasible, users should restrict the capture environment to trusted networks only or disable automatic decoding for IEEE 1609.2 protocols if such traffic is not actively required for analysis. Additionally, implementing network segmentation to isolate sensitive monitoring infrastructure from potentially hostile wireless environments can reduce the attack surface and prevent exposure to crafted packets designed to trigger this crash condition.