CVE-2026-130464 in Wiresharkinfo

Summary

by MITRE • 11/20/2026

MsgPack and NNTP 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 a critical flaw within the network protocol dissectors for MessagePack and NNTP (Network News Transfer Protocol) in Wireshark versions ranging from 4.6.0 through 4.6.9, as well as earlier releases spanning from 4.4.0 to 4.4.19. This defect manifests specifically when the application processes malformed or specially crafted input data designed to trigger an exception during the parsing phase of these protocols. The root cause lies in insufficient validation and bounds checking within the dissectors responsible for interpreting MessagePack binary serialization formats and NNTP message structures. When a user opens a capture file containing such maliciously constructed packets, or when Wireshark is configured to actively monitor network traffic that includes these malformed segments, the application encounters an unrecoverable error state leading to an immediate crash. This behavior classifies as a classic denial of service vulnerability where the availability of the analysis tool is compromised without requiring any authentication or privileged access from the attacker, who merely needs to supply the problematic data stream or file.

From a technical perspective, this issue aligns with CWE-20 Improper Input Validation and CWE-400 Resource Exhaustion resulting in Denial of Service. The dissectors fail to adequately verify the integrity and length of incoming fields before attempting to access memory locations associated with those fields. In the case of MessagePack, which is a compact binary serialization format often used for efficient data exchange between servers and web applications, the parser likely attempts to read beyond allocated buffers or dereference null pointers when encountering unexpected byte sequences that deviate from valid schema definitions. Similarly, the NNTP dissector may fail to handle edge cases in header parsing or body length calculations, leading to memory corruption or stack overflow conditions. These flaws are particularly dangerous because Wireshark is frequently used by security professionals and network administrators who routinely analyze traffic captured from untrusted networks. An attacker could embed these malformed packets within a standard PCAP file distributed via email or downloaded from the internet, thereby turning a routine analysis task into an attack vector that disrupts workflow and potentially exposes sensitive network data if the crash occurs during active monitoring of live traffic.

The operational impact of this vulnerability extends beyond simple application instability. For security analysts relying on Wireshark for incident response and forensic investigations, a sudden crash can result in the loss of unsaved work or incomplete capture files that are critical to understanding an ongoing attack. Furthermore, if the vulnerability is exploited during active packet monitoring, it could prevent the analyst from capturing subsequent packets necessary for complete threat intelligence gathering. In enterprise environments where Wireshark might be integrated into automated analysis pipelines or used by multiple users on shared systems, this denial of service can disrupt broader security operations and create gaps in visibility that attackers could exploit to move laterally within a network undetected. The lack of robust error handling means that the application does not gracefully degrade or isolate the faulty packet but instead terminates entirely, leaving no opportunity for recovery without restarting the software.

Mitigation strategies primarily involve updating the Wireshark installation to a version where these dissectors have been patched with proper input validation and memory safety checks. Users should immediately upgrade to versions released after 4.6.9 and 4.4.19, as these releases contain fixes for the specific parsing errors in both MessagePack and NNTP modules. Until an update can be applied, analysts should exercise extreme caution when opening capture files from unknown or untrusted sources, preferably using isolated virtual machines to prevent system-wide instability if a crash occurs. Additionally, disabling the dissectors for MessagePack and NNTP within Wireshark preferences can serve as a temporary workaround, although this reduces visibility into traffic utilizing these protocols. It is also advisable to implement network segmentation rules that filter out malformed packets at the perimeter before they reach analysis endpoints, thereby reducing the attack surface exposed by vulnerable software versions. This incident underscores the importance of rigorous fuzzing and formal verification techniques in protocol implementation development to ensure resilience against adversarial inputs.

Responsible

GitLab

Reservation

11/17/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00199

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!