CVE-2026-130446 in Wireshark
Summary
by MITRE • 11/20/2026
ACN 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 ACN (Advanced Control Network) protocol dissector, a component responsible for parsing and displaying traffic related to the DMX512/A standard used in stage lighting and effects control, contains a critical memory safety flaw that leads to application crashes. This vulnerability affects Wireshark versions 4.6.0 through 4.6.9 as well as the legacy branch versions 4.4.0 through 4.4.19. The root cause of this instability is typically associated with improper bounds checking or null pointer dereferencing when processing malformed ACN packets. When a user opens a capture file containing specifically crafted malicious data, or views live traffic from an untrusted source that exploits these parsing errors, the dissector fails to handle the anomalous input gracefully. Instead of discarding the invalid packet and continuing operation, the software encounters an unrecoverable error state, resulting in an immediate termination of the application process.
From a technical perspective, this issue represents a classic denial-of-service vector arising from insufficient validation of protocol fields during the decoding phase. In network analysis tools like Wireshark, dissectors must be robust against malformed data because analysts often inspect captures collected from hostile or unmanaged networks where attackers may intentionally inject corrupted packets to disrupt monitoring infrastructure. The ACN protocol dissector likely fails to verify that certain array indices are within valid limits or checks for null pointers before accessing memory structures associated with packet fields. This lack of defensive programming allows an attacker who can influence the network traffic being analyzed to trigger a segmentation fault or similar exception, effectively crashing the analysis tool and halting any ongoing security monitoring or troubleshooting activities.
The operational impact of this vulnerability is significant for professionals relying on Wireshark for incident response, forensic analysis, and routine network diagnostics. A crash in the primary packet analysis tool can lead to data loss if unsaved captures are involved, but more critically, it creates a window of opportunity where an analyst cannot monitor live traffic or review historical logs effectively. In high-stakes environments such as critical infrastructure monitoring or enterprise security operations centers, the inability to parse ACN protocol traffic due to application instability undermines situational awareness. Attackers targeting organizations with extensive lighting control systems could potentially use this vector not only to disrupt internal IT tools but also to mask malicious activity within the physical layer of building automation networks by causing the defensive analysis tools to fail repeatedly when encountering their crafted packets.
Mitigation strategies primarily involve upgrading to a patched version of Wireshark where these memory safety issues have been resolved through rigorous code review and fuzzing efforts. Until an upgrade is feasible, users should exercise extreme caution when opening capture files from untrusted sources or analyzing traffic on networks known to be compromised. Implementing network segmentation to isolate ACN protocol traffic from general IT monitoring streams can also reduce exposure. Furthermore, security teams should ensure that their packet analysis workflows include automated validation steps before deep inspection of potentially malicious captures. This vulnerability is categorized under CWE-125 Out-of-bounds Read or CWE-476 NULL Pointer Dereference depending on the specific implementation detail, and it aligns with ATT&CK technique T1498 Network Denial of Service, specifically through resource exhaustion via application crash rather than bandwidth saturation.