CVE-2026-130455 in Wiresharkinfo

Summary

by MITRE • 11/20/2026

Kafka protocol dissector infinite loop 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 the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified involves an infinite loop within the Kafka protocol dissector, affecting Wireshark versions ranging from 4.4.0 through 4.4.19 and 4.6.0 through 4.6.9. This flaw resides in the network packet analysis software's ability to parse traffic adhering to the Apache Kafka messaging protocol. When a user opens or processes a capture file containing specifically crafted malicious packets, or when Wireshark is configured to monitor live traffic that includes these malformed sequences, the dissector enters an uncontrolled execution loop. This behavior prevents the application from returning control to the operating system's scheduler for other tasks, effectively freezing the interface and consuming significant CPU resources until the process is forcibly terminated by the user or the system.

From a technical perspective, this issue classifies as a Denial of Service vulnerability resulting from improper input validation and lack of bounds checking during protocol parsing. The dissector fails to detect malformed or excessively nested structures within the Kafka binary data stream before attempting recursive processing or iterative decoding. This aligns with CWE-835, which describes loops that do not terminate due to logic errors in loop control conditions. Additionally, it relates to CWE-674 regarding uncontrolled recursion depth if the parsing mechanism relies on recursive descent algorithms without adequate stack limits. The root cause is typically a failure to verify packet length fields or sequence integrity before initiating complex state machine transitions within the protocol parser.

The operational impact of this vulnerability is primarily focused on service availability and resource exhaustion for security analysts, network engineers, and developers who rely on Wireshark for traffic analysis. An attacker capable of injecting such malformed packets into a monitored network segment can cause local denial of service conditions on any workstation running affected versions of the software. This not only disrupts ongoing investigations but also poses a risk to system stability if the high CPU usage triggers thermal throttling or causes other critical applications to fail due to resource contention. In environments where Wireshark is used for real-time intrusion detection monitoring, this flaw could blind security operations centers by freezing their primary analysis tool during an active incident response scenario.

This vulnerability maps directly to MITRE ATT&CK technique T1499, Endpoint Denial of Service, specifically under the sub-technique of resource exhaustion via application layer attacks. It also reflects aspects of T1059, Command and Scripting Interpreter, if exploited in conjunction with other vulnerabilities to execute arbitrary code after destabilizing the host environment through resource starvation. The attack vector is typically remote or local depending on whether the malicious traffic originates from an external source or a compromised internal node sharing network access with the analyst's machine.

Mitigation strategies involve immediate upgrading of Wireshark to versions 4.6.10 and later, where this infinite loop logic has been corrected by implementing strict validation checks before parsing Kafka-specific fields. Until upgrades are feasible, users should avoid opening untrusted capture files or disabling the Kafka protocol dissector within the preferences menu if live monitoring is not strictly required for that specific protocol. Security teams should also implement network segmentation to prevent exposure of analysis workstations to potentially hostile traffic sources and ensure that endpoint protection solutions can detect abnormal CPU usage patterns indicative of such application-level loops. Regular patch management cycles are essential to address these types of parser vulnerabilities promptly, as they often serve as initial footholds for more complex exploitation chains in broader security architectures.

Responsible

GitLab

Reservation

11/17/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00185

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!