Wireshark fixes dozens of parser flaws including profile import RCE and dissector DoS
Patch & Detection Intelligence · 33 sources · Updated 3mo ago · First seen May 24, 2026

Wireshark disclosed and patched a broad set of vulnerabilities across its packet analysis engine, protocol dissectors, codecs, decompression routines, and the sharkd backend, with the most serious issues including possible code execution, memory corruption, and denial of service. The release notes for Wireshark 4.6.6 aggregate advisories wnpa-sec-2026-08 through wnpa-sec-2026-50, while earlier coordinated fixes shipped in 4.6.5 and 4.4.15 for affected 4.6.0-4.6.4 and 4.4.0-4.4.14 branches. One high-severity flaw, tracked as CVE-2026-5656, allowed a crafted configuration-profile ZIP to escape the intended extraction path and plant a Lua plugin for execution on the next launch. Additional issues included crashes and memory-safety bugs in AMR-NB (CVE-2026-5654), iLBC (CVE-2026-5657), ASN.1 PER (CVE-2026-6527), DCP-ETSI (CVE-2026-5653, CVE-2026-6530), and later sharkd and Bluetooth AVRCP flaws that could crash the process or potentially enable control-flow hijack.
Several vulnerabilities were reachable simply by opening a malicious packet capture or by parsing malformed traffic on the wire. Wireshark documented infinite-loop and CPU-exhaustion conditions in the USB HID dissector (CVE-2026-6534), OpenFlow v5 dissector (CVE-2026-6521), and LZ77 decompression path (CVE-2026-6533), alongside crashes in BEEP (CVE-2026-6538) and other protocol handlers. GitLab issue reports show researchers and fuzzing jobs repeatedly triggering heap overflows, double-free conditions, NULL dereferences, and non-advancing-offset parser failures in components such as DCP-ETSI, H.245, MIH, eDonkey, and sharkd, underscoring that malformed captures can destabilize both the GUI and tshark. Wireshark said it was not aware of active exploitation at disclosure time and urged users to update to the fixed releases.


