CVE-2026-6532: Buffer Over-read in Wireshark
Published Apr 30, 2026
·Updated
Kismet 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
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.6.5
Event History
Apr 30, 2026
CVE Published
via MITRE·05:36 AM
Data Sourced
via MITRE·05:36 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-6532?
CVE-2026-6532 is classified as a denial of service vulnerability due to a buffer over-read.
2
How do I fix CVE-2026-6532?
To mitigate CVE-2026-6532, upgrade Wireshark to version 4.6.5 or later, or to 4.4.15 or later.
3
What versions of Wireshark are affected by CVE-2026-6532?
CVE-2026-6532 affects Wireshark versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
4
What impact does CVE-2026-6532 have on Wireshark users?
Users of affected Wireshark versions may experience crashes, leading to denial of service.
5
Is there a workaround for CVE-2026-6532 if I cannot upgrade Wireshark?
There are no known workarounds for CVE-2026-6532, so upgrading is the recommended solution.