CVE-2026-130449 in Wiresharkinfo

Summary

by MITRE • 11/20/2026

TLS protocol dissector memory leak in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified involves a critical memory leak within the Transport Layer Security (TLS) protocol dissector, specifically affecting Wireshark versions ranging from 4.6.0 through 4.6.9 and 4.4.0 through 4.4.19. This flaw resides in the component responsible for parsing and analyzing TLS traffic captures or live network streams. When a user opens a maliciously crafted packet capture file or views specific types of encrypted network traffic, the dissector fails to properly release allocated memory resources after processing certain malformed or edge-case data structures associated with TLS handshake messages or record layers. This improper resource management leads to a gradual accumulation of unreleased memory blocks within the application process space during the analysis session.

From a technical perspective, this issue is classified as an out-of-bounds read or improper allocation and deallocation error that results in uncontrolled resource consumption. The vulnerability allows for a denial of service condition by exhausting system resources available to the Wireshark process. As the dissector continues to parse subsequent packets containing the problematic TLS structures, it repeatedly allocates new memory without freeing previously allocated but unused buffers. Over time, this leads to significant increases in RAM usage and potentially high CPU utilization as the operating system attempts to manage the growing footprint of a single application instance. If left unchecked during prolonged analysis sessions or when processing large capture files with many such packets, the process may become unresponsive due to memory pressure, trigger an out-of-memory kill by the operating system kernel, or crash entirely, thereby preventing further network traffic analysis and disrupting operational workflows.

The impact of this vulnerability is primarily centered on availability rather than confidentiality or integrity in most standard usage scenarios. For security analysts relying on Wireshark for incident response, forensic investigation, or routine monitoring, a denial of service event can halt critical operations. In environments where automated tools utilize the library version of Wireshark to parse traffic programmatically, this memory leak could lead to service degradation across multiple processes if not handled with proper resource limits. While direct code execution is not implied by this specific flaw, the instability introduced can indirectly compromise security posture by forcing analysts to restart their analysis sessions, potentially losing unsaved work or interrupting time-sensitive investigations into active threats.

This vulnerability aligns with Common Weakness Enumeration (CWE) category CWE-401, which describes a missing release of memory after effective usage, and also relates to CWE-789 regarding the use of uninitialized memory if the leak involves accessing freed regions in subsequent operations due to state corruption from repeated leaks. In terms of adversarial tactics, this falls under MITRE ATT&CK technique T1499, Endpoint Denial of Service, specifically via resource exhaustion through application layer vulnerabilities. Attackers or threat actors could potentially exploit this by crafting specific TLS packet sequences designed to trigger the leak repeatedly, aiming to disrupt security monitoring tools deployed on endpoints or servers where Wireshark is used for troubleshooting network issues.

Mitigation strategies primarily involve upgrading to a patched version of Wireshark that resolves the memory management logic within the TLS dissector. Users should ensure they are running versions later than 4.6.9 and 4.4.19, as these releases contain fixes for the improper resource release mechanism. In scenarios where immediate patching is not feasible due to operational constraints or compatibility requirements with legacy systems, analysts can mitigate risk by avoiding the opening of untrusted packet capture files that may contain maliciously crafted TLS structures. Additionally, configuring operating system-level memory limits or using containerization technologies to restrict the maximum memory footprint of Wireshark processes can help prevent a single instance from consuming all available system resources and crashing the host environment. Regular updates to network analysis tools are essential to maintain robust security operations against such resource exhaustion vulnerabilities.

Responsible

GitLab

Reservation

11/17/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00252

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!