CVE-2026-130439 in Wireshark
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 identified involves multiple critical flaws within the network packet analysis software, specifically affecting versions ranging from 4.4.0 through 4.4.19 and 4.6.0 through 4.6.9. These defects reside in various protocol dissectors, which are specialized modules responsible for parsing and interpreting raw network traffic data into human-readable formats. When the application processes malformed or specially crafted packets designed to exploit these specific code paths, it triggers a crash resulting in an immediate denial of service condition. This issue highlights significant weaknesses in input validation mechanisms across multiple protocols supported by the software suite, allowing attackers who can inject malicious traffic into monitored networks to disrupt analytical operations effectively.
From a technical perspective, protocol dissectors must handle arbitrary data structures that may not conform to expected standards or specifications. In this instance, certain dissectors failed to adequately verify buffer boundaries, array indices, or pointer validity before dereferencing them during the parsing process. This lack of rigorous boundary checking leads to memory corruption events such as out-of-bounds reads or writes, which subsequently cause the application to terminate unexpectedly. The presence of multiple distinct vulnerabilities across different protocol handlers suggests a systemic issue in how error handling and validation logic are implemented throughout the codebase rather than an isolated incident within a single module.
The operational impact of this vulnerability is substantial for organizations relying on continuous network monitoring and forensic analysis capabilities. A denial of service condition prevents security analysts from capturing, storing, or analyzing traffic data during critical incidents. If an attacker can trigger these crashes repeatedly, they can create blind spots in the organization's detection infrastructure, potentially masking other malicious activities such as lateral movement or data exfiltration that might be occurring concurrently. Furthermore, the instability introduced by frequent application restarts degrades the overall reliability of security operations centers and incident response workflows.
This vulnerability aligns with Common Weakness Enumeration category CWE-125, which describes out-of-bounds read conditions where software reads memory beyond the intended boundary. It also relates to CWE-787, concerning out-of-bounds writes that can lead to arbitrary code execution or system crashes depending on the specific exploitation context. In terms of adversary tactics, this flaw supports techniques associated with ATT&CK tactic TA0005, Defense Evasion, specifically under subtechniques aimed at disrupting availability and obscuring detection mechanisms by crashing monitoring tools.
Mitigation strategies should prioritize immediate patching to the latest stable release where these specific dissectors have been updated with robust input validation checks. Until patches are applied, network administrators can implement access control lists or firewall rules to restrict traffic from untrusted sources that might contain malformed packets targeting these protocols. Additionally, enabling core dump analysis and logging mechanisms can help in identifying which protocol dissector is failing, allowing for temporary disabling of the affected module if necessary to maintain partial functionality while preserving system stability against further exploitation attempts.