CVE-2026-7376: NULL Pointer Dereference 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/sharkdto 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·07:34 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-7376?
CVE-2026-7376 is classified as a denial of service vulnerability.
2
How do I fix CVE-2026-7376?
To fix CVE-2026-7376, you should upgrade Wireshark sharkd to version 4.6.5 or higher, or to version 4.4.15 or higher.
3
Which versions of Wireshark are affected by CVE-2026-7376?
CVE-2026-7376 affects Wireshark sharkd versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
4
What impact does CVE-2026-7376 have on Wireshark?
CVE-2026-7376 can cause a crash in Wireshark, leading to a denial of service.
5
Is CVE-2026-7376 a critical vulnerability?
While CVE-2026-7376 is serious due to its denial of service impact, its criticality depends on the use case and environment in which Wireshark is deployed.