CVE-2026-6527: Uncontrolled Recursion in Wireshark
Published Apr 30, 2026
·Updated
ASN.1 PER 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
wiresharkto a version that resolves this vulnerability.Fixed in 4.6.5
Event History
Apr 30, 2026
CVE Published
via MITRE·05:35 AM
Data Sourced
via MITRE·05:35 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Dec 24, 58314
Event
via FIRST·05:12 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-6527?
CVE-2026-6527 has a severity level that allows for denial of service due to uncontrolled recursion in the Wireshark ASN.1 PER protocol dissector.
2
How do I fix CVE-2026-6527?
To fix CVE-2026-6527, upgrade Wireshark to versions 4.6.5 or newer, or 4.4.15 or newer.
3
What versions of Wireshark are affected by CVE-2026-6527?
CVE-2026-6527 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-6527?
The impact of CVE-2026-6527 is a crash of Wireshark that leads to a denial of service.
5
Is CVE-2026-6527 a critical vulnerability?
CVE-2026-6527 is not classified as critical but presents a significant denial of service risk.