Wireshark, an open-source network protocol analyzer, has released version 4.6.10, a security-focused update addressing 39 vulnerabilities affecting protocol dissectors, capture file parsers, and other components.
Most vulnerabilities cause crashes or infinite loops that make Wireshark terminate unexpectedly or become unresponsive when processing specially crafted network traffic or capture files. Affected dissectors include RTSE, NBAP, Matter, IEEE 1609.2, OpenWire, PROFINET, and SDP.
The Kafka dissector receives a fix for an infinite-loop vulnerability tracked as CVE-2026-130455. Similar problems affecting multiple other dissectors have also been addressed. The update also fixes crashes in the core packet dissection engine.
Memory-related vulnerabilities are another concern. The TLS dissector has a memory leak tracked as CVE-2026-130449. The SCTP dissector contains a heap information disclosure vulnerability. Several additional advisories address memory leaks across multiple protocol dissectors.
Beyond protocol analysis, Wireshark 4.6.10 fixes security issues in several capture file parsers, including ERF, Android Logcat, PEAK CAN TRC, Ascend, and Tektronix K12xx. These fixes are especially relevant when examining capture files from external or untrusted sources.
In addition to the security advisories, the release fixes several functional bugs. Among them is a remote code execution vulnerability involving a numeric truncation error in LoRaWAN decryption. The developers also fixed a crash in Lua exception handling, an issue where encrypted NAS-EPS messages were incorrectly dissected as plaintext, and display problems with packet separators when using KDE’s Breeze style.
On Windows and macOS, the installers now include Brotli 1.2.1 to address CVE-2026-111497. Windows installers also update the bundled Npcap packet capture library from version 1.88 to 1.89.
For Linux users and distribution maintainers, the release notes clarify a change introduced in Wireshark 4.6 concerning external capture (extcap) helpers. On Unix-like systems, these executables are now searched for under the libexec directory by default, typically /usr/libexec/wireshark/extcap.
The developers note that third-party extcap packages may require packaging adjustments. The location can also be overridden using the WIRESHARK_EXTCAP_DIR environment variable. Distributions without a libexec directory, such as Alpine Linux, continue using their previous locations.
Finally, Wireshark 4.6.10 introduces no new protocol support, although numerous existing protocol dissectors and capture file formats have been updated.
For more information, see the release notes.
