CVE-2026-6519: Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark
Published Apr 30, 2026
·Updated
MBIM 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:33 AM
Data Sourced
via MITRE·05:33 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Dec 24, 58314
Event
via FIRST·12:32 AM
Frequently Asked Questions
1
What is the severity of CVE-2026-6519?
CVE-2026-6519 is classified as a denial of service vulnerability.
2
How do I fix CVE-2026-6519?
To fix CVE-2026-6519, upgrade Wireshark to a version beyond 4.6.4 or 4.4.14.
3
Which versions of Wireshark are affected by CVE-2026-6519?
CVE-2026-6519 affects Wireshark versions 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14.
4
What impact does CVE-2026-6519 have on system performance?
CVE-2026-6519 can cause an infinite loop, leading to denial of service and unresponsive behavior.
5
Is there a workaround for CVE-2026-6519?
Currently, there are no known workarounds for CVE-2026-6519; updating to the latest version is recommended.