CVE-2026-6531: Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark
Published Apr 30, 2026
·Updated
SANE protocol dissector infinite loop 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
Dec 24, 58314
Event
via FIRST·08:48 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-6531?
CVE-2026-6531 is classified as a denial of service vulnerability.
2
How do I fix CVE-2026-6531?
To fix CVE-2026-6531, upgrade Wireshark to version 4.6.5 or later, or version 4.4.15 or later.
3
What versions of Wireshark are affected by CVE-2026-6531?
CVE-2026-6531 affects Wireshark versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
4
What causes the vulnerability CVE-2026-6531 in Wireshark?
CVE-2026-6531 is caused by an infinite loop in the SANE protocol dissector.
5
What impact does CVE-2026-6531 have on users of Wireshark?
The impact of CVE-2026-6531 is denial of service, potentially crashing the application.