CVE-2026-6537: Stack-based Buffer Overflow in Wireshark
Published Apr 30, 2026
·Updated
ZigBee protocol dissector crash in Wireshark 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 Wireshark>=4.6.0<=4.6.4, >=4.4.0<=4.4.14
Wireshark Wireshark>=4.4.0<=4.4.14
Wireshark Wireshark>=4.6.0<=4.6.4
Remediation
Information
Upgrade to version 4.6.5 or above
Event History
Apr 30, 2026
CVE Published
via MITRE·05:37 AM
Data Sourced
via MITRE·05:37 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Dec 24, 58314
Event
via FIRST·05:14 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-6537?
CVE-2026-6537 is classified as a high severity vulnerability due to its potential to cause a denial of service.
2
How do I fix CVE-2026-6537?
To fix CVE-2026-6537, update Wireshark to the latest version beyond 4.6.4 or 4.4.14.
3
What versions of Wireshark are affected by CVE-2026-6537?
CVE-2026-6537 affects Wireshark versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
4
What is the impact of CVE-2026-6537?
The impact of CVE-2026-6537 is a stack-based buffer overflow that can lead to application crashes.
5
How does CVE-2026-6537 exploit the Wireshark software?
CVE-2026-6537 exploits the Wireshark ZigBee protocol dissector by triggering a buffer overflow through specially crafted packets.