CVE-2026-7378: Heap-based Buffer Overflow in Wireshark
Published Apr 30, 2026
·Updated
Crash 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
Wireshark (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·09:47 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-7378?
CVE-2026-7378 is classified as a denial of service vulnerability due to a heap-based buffer overflow.
2
How do I fix CVE-2026-7378?
To mitigate CVE-2026-7378, upgrade Wireshark sharkd to version 4.6.5 or later, or to version 4.4.15 or later.
3
What versions of Wireshark sharkd are affected by CVE-2026-7378?
CVE-2026-7378 affects Wireshark sharkd versions from 4.6.0 to 4.6.4 and from 4.4.0 to 4.4.14.
4
What are the potential impacts of CVE-2026-7378?
The potential impact of CVE-2026-7378 includes application crashes and service interruptions.
5
Is there a workaround for CVE-2026-7378?
There are no known workarounds for CVE-2026-7378; updating to a fixed version is recommended.