CVE-2026-6526: NULL Pointer Dereference in Wireshark
Published Apr 30, 2026
·Updated
RTSP protocol dissector crash in Wireshark 4.6.0 to 4.6.4
Affected Software
2 affected components
Wireshark Wireshark>=4.6.0<=4.6.4
Wireshark Wireshark>=4.6.0<=4.6.4
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wiresharkto a version that resolves this vulnerability.Fixed in 4.6.5
Event History
Apr 30, 2026
CVE Published
via MITRE·05:34 AM
Data Sourced
via MITRE·05:34 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Dec 24, 58314
Event
via FIRST·05:33 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-6526?
CVE-2026-6526 has a high severity due to the potential for a crash caused by a NULL pointer dereference.
2
How does CVE-2026-6526 affect Wireshark?
CVE-2026-6526 affects Wireshark versions 4.6.0 to 4.6.4, leading to crashes when using the RTSP protocol dissector.
3
How do I fix CVE-2026-6526?
To fix CVE-2026-6526, users should upgrade Wireshark to version 4.6.5 or later.
4
Which versions of Wireshark are affected by CVE-2026-6526?
CVE-2026-6526 affects Wireshark versions between 4.6.0 and 4.6.4.
5
What kind of vulnerability is CVE-2026-6526?
CVE-2026-6526 is a NULL Pointer Dereference vulnerability that results in application crashes.