Wireshark 4.6.10 Released With Patch for 39 Security Vulnerabilities
Wireshark 4.6.10 has been released, addressing 39 security vulnerabilities including infinite loops, memory leaks, and heap disclosures across its protocol dissectors and capture file parsers.

Wireshark, the ubiquitous network protocol analyzer, has released version 4.6.10, a significant update that patches a total of 39 security vulnerabilities. These flaws span various components of the software, including its extensive library of protocol dissectors, capture file parsers, the core dissection engine, and even audio codecs. The vulnerabilities could lead to a range of issues, from application crashes and processing hangs to resource exhaustion, impacting the reliability and security of systems used for network analysis and troubleshooting.
The official release notes detail a series of security advisories, numbered wnpa-sec-2026-111 through wnpa-sec-2026-149, encompassing the 39 fixes. Developers indicated that the large volume of patches is a result of both an internal review and an increase in AI-assisted vulnerability reports from external researchers. While not all vulnerabilities carry the same severity, the update addresses critical issues such as infinite loops and memory leaks, which can significantly disrupt network analysis workflows.
Many of the patched vulnerabilities target specific protocol dissectors, the modules responsible for interpreting raw network data into human-readable protocol fields. Affected protocols include RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, ACN, PROFINET, and SDP. Several advisories group together crashes affecting multiple dissectors, underscoring the broad impact of this update across different network environments and protocols.
Among the specifically identified vulnerabilities, CVE-2026-130455 addresses an infinite loop within the Kafka dissector, while CVE-2026-130451 tackles infinite loops across multiple protocol dissectors. Additionally, CVE-2026-130462 covers hangs that can occur in both dissectors and file parsers, potentially leaving analysis tools unresponsive.
Beyond dissectors, Wireshark's capture file handling capabilities have also received attention. The update includes patches for crashes in ERF, Android Logcat, and PEAK CAN TRC parsing. Furthermore, issues with large loops in the Ascend and Tektronix K12xx readers have been resolved. The PEAK CAN TRC vulnerability, CVE-2026-130467, is noted to specifically affect builds using older GLib versions, a detail important for assessing exposure across diverse operating system configurations.
Memory management issues have also been addressed, with CVE-2026-130449 fixing a memory leak in the TLS dissector and CVE-2026-130436 covering memory leaks across multiple dissectors. A grouped advisory, CVE-2026-130445, combines crashes, infinite loops, and memory leaks, highlighting the multifaceted nature of some vulnerabilities. An SCTP dissector heap disclosure, tracked as wnpa-sec-2026-147, is also among the fixes. Additionally, vulnerabilities affecting audio codecs, specifically iLBC and AMR, are addressed under wnpa-sec-2026-148 and wnpa-sec-2026-149, though these do not have associated CVE identifiers in the release notes.
The release of Wireshark 4.6.10 follows previous security updates, including versions 4.6.9 and 4.6.8, which addressed 19 and 28 vulnerabilities respectively. This latest update also incorporates changes to bundled components. Windows and macOS installers now include Brotli version 1.2.1, which fixes CVE-2026-111497. Windows packages have also been updated to Npcap version 1.89 from 1.88. These component updates are crucial for a comprehensive security posture.
Users are strongly advised to update to Wireshark 4.6.10 as soon as possible. Installation packages and source code are available from the official Wireshark download page. Linux and Unix users can typically update via their distribution's package manager. Security teams should prioritize updating analysis workstations and verifying deployed versions, especially for environments that handle external capture files, to mitigate potential risks associated with these newly patched vulnerabilities.