CVE-2026-7379: Missing Release of Memory after Effective Lifetime in Wireshark

Q: What is the severity of CVE-2026-7379?

CVE-2026-7379 is classified as a high severity vulnerability due to its potential to cause a denial of service.

Q: How do I fix CVE-2026-7379?

To fix CVE-2026-7379, update Wireshark sharkd to version 4.6.5 or later if you are using versions between 4.6.0 and 4.6.4, or 4.4.15 or later if on versions between 4.4.0 and 4.4.14.

Q: What causes the memory leak in CVE-2026-7379?

The memory leak in CVE-2026-7379 is caused by a missing release of memory after the effective lifetime of certain resources.

Q: Which versions of Wireshark sharkd are affected by CVE-2026-7379?

Versions of Wireshark sharkd affected by CVE-2026-7379 are from 4.6.0 to 4.6.4 and from 4.4.0 to 4.4.14.

Q: What impact does CVE-2026-7379 have on users?

CVE-2026-7379 can lead to denial of service, preventing users from using affected versions of Wireshark sharkd.

Published Apr 30, 2026

Updated

Memory leak in sharkd 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service

Affected Software

3 affected components

Wireshark sharkd>=4.6.0<=4.6.4, >=4.4.0<=4.4.14

Wireshark Wireshark>=4.4.0<4.4.15

Wireshark Wireshark>=4.6.0<4.6.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade sharkd to a version that resolves this vulnerability.
Fixed in 4.6.5

Event History

Apr 30, 2026

CVE Published

via MITRE·05:04 AM

Data Sourced

via MITRE·05:04 AM

RemedyDescriptionSeverityWeakness

Data Sourced

via NVD·06:16 AM

DescriptionSeverityWeaknessAffected Software

Dec 24, 58314

Event

via FIRST·02:23 AM

Frequently Asked Questions

What is the severity of CVE-2026-7379?

CVE-2026-7379 is classified as a high severity vulnerability due to its potential to cause a denial of service.

How do I fix CVE-2026-7379?