The following vulnerabilities have been fixed:
wnpa-sec-2026-92 ZigBee ZCL protocol dissector crash. CVE-2026-95391.
wnpa-sec-2026-93 SCTP protocol dissector crash. Issue 21481. CVE-2026-95389.
wnpa-sec-2026-94 TTL file parser infinite loop. Issue 21501. CVE-2026-95386.
wnpa-sec-2026-95 PEAK CAN TRC file parser crash. Issue 21503. CVE-2026-95390.
wnpa-sec-2026-96 IEEE C37.118 Synchrophasor protocol dissector memory leak. Issue 21492. CVE-2026-95395.
wnpa-sec-2026-97 SPDY protocol dissector crash. Issue 21487. CVE-2026-95387.
wnpa-sec-2026-98 Microsoft Network Monitor file parser large loop. Issue 21523. CVE-2026-95394.
wnpa-sec-2026-99 CSN.1 protocol dissector crash. Issue 21510. CVE-2026-95393.
wnpa-sec-2026-100 MBIM protocol dissector crash. wsbuglink:21549, Issue 21550. CVE-2026-95392.
wnpa-sec-2026-101 Sharkd utility crash. Issue 21545. CVE-2026-95388.
wnpa-sec-2026-102 Frame protocol metadissector crash. Issue 21525. CVE-2026-96422.
wnpa-sec-2026-103 USB HID protocol dissector infinite loop and memory leak. Issue 21566. CVE-2026-96421.
wnpa-sec-2026-104 RF4CE protocol dissector crash. Issue 21574. CVE-2026-96417.
wnpa-sec-2026-105 Toshiba file parser crash. Issue 21541. CVE-2026-96420.
wnpa-sec-2026-106 Profile import crash and possible code execution. Issue 21553. CVE-2026-96419.
wnpa-sec-2026-107 TIFF protocol dissector infinite loop. Issue 21565. CVE-2026-96418.
wnpa-sec-2026-108 X11 protocol dissector crash. Issue 21563. CVE-2026-96423.
wnpa-sec-2026-109 IEEE 802.11 protocol dissector crash. Issue 21564. CVE-2026-96416.
wnpa-sec-2026-110 Catapult DCT2000 protocol dissector crash. Issue 21589. CVE-2026-96415.
The following bugs have been fixed:
DICOM Export Objects uint32 length wrap causes undersized allocation and heap overwrite. Issue 21497.
DICOM AT value formatting has quadratic packet-scope memory amplification. Issue 21498.
F1AP: NotificationInformation IE under PWSSystemInformation.iE-Extensions not decoded in WriteReplaceWarningRequest. Issue 21499.
ZDI-CAN-32846: Wireshark LBMC Fragment Reassembly Integer Overflow Remote Code Execution Vulnerability. Issue 21519.
ZDI-CAN-32851: Wireshark LoRaWAN Decryption Numeric Truncation Error Remote Code Execution Vulnerability. Issue 21520.
RTPS: dissect_RTPS_DATA_BATCH() sample-info minimum-length check increments the wrong variable (min_len instead of min_length) Issue 21521.
NULL-pointer dereference in pkcs12 PBE_decrypt_data via empty AlgorithmIdentifier. Issue 21535.
AKP EncryptedData footer can use an uninitialized tvbuff pointer after malformed OCTET STRING parsing. Issue 21539.
Out-of-bounds read in DFVM binary-operation error path. Issue 21540.
Wireshark is not ignoring GREASE values in the JA4 calculation. Issue 21548.
Bluetooth AVCTP multipart reassembly integer overflow (incomplete AVRCP ckd_add sibling fix) Issue 21552.
Fuzz job UTF-8 encoding issue: fuzz-2026-09-06-16330342486.pcap. Issue 21562.
ZDI-CAN-31676: Wireshark SMB Object Export Integer Overflow. Issue 21575.
Heap out-of-bounds read in FP Hint E-DCH DDI count handling. Issue 21580.
F1AP fails to decode RRC release message. Issue 21581.
Stack-based buffer overflow in etwdump extcap (etw_ndiscap.c) when parsing crafted ETL files. Issue 21587.
There are no new protocols in this release.
AKP, Bencode, BSSLAP, BT AVCTP, Catapult DCT2000, CSN.1, DICOM, F1AP, FP Hint, Frame, GNW, GSM BSSMAP, IEEE 802.11, LBMC, LoRaWAN, NBAP, OBEX, OpenFlow 1.3, OpenFlow 1.4, OpenFlow 1.5, PKCS12, QUIC, RTPS, SGP.32, SMB, SPDY, SYNCHROPHASOR, UMTS FP, X11, and ZigBee ZCL
BLF, Network Monitor, pcapng, PEAK TRC, Toshiba, and TTL
There is no new or updated file format support in this release.
On UN*X systems (excluding macOS when running from an app bundle, as
with the official installer) extcap binaries are now searched for under
the libexec directory by default, e.g., /usr/libexec/wireshark/extcap
instead of /usr/lib64/wireshark/extcap or similar. This is the customary
place for helper binaries, which as opposed to libraries do not need
multiarch support. The location can be overridden via the environment
variable WIRESHARK_EXTCAP_DIR. The extcap binaries shipped with Wireshark
are installed in the new location, but third party extcaps may need
packaging changes. This change was effective in version 4.6.0, but was not
explicitly noted in the release notes previously. Note that some distributions
do not use a libexec directory, such as Alpine Linux, which does not have
multilib support. On such systems extcap binaries should be in the same
location as before.