Wireshark 4.6.x Memory Leak (sharkd) DoS
CVE-2026-7379 Published on April 30, 2026

Missing Release of Memory after Effective Lifetime in Wireshark
Memory leak in sharkd 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service

NVD

Vulnerability Analysis

CVE-2026-7379 can be exploited with local system access, requires user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.

Attack Vector:
LOCAL
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
REQUIRED
Scope:
UNCHANGED
Confidentiality Impact:
NONE
Integrity Impact:
NONE
Availability Impact:
HIGH

Weakness Type

What is a Memory Leak Vulnerability?

The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is often triggered by improper handling of malformed data or unexpectedly interrupted sessions. In some languages, developers are responsible for tracking memory allocation and releasing the memory. If there are no more pointers or references to the memory, then it can no longer be tracked and identified for release.

CVE-2026-7379 has been classified to as a Memory Leak vulnerability or weakness.


Products Associated with CVE-2026-7379

Want to know whenever a new CVE is published for Wireshark? stack.watch will email you.

 

Affected Versions

Wireshark Foundation Wireshark: