Wireshark UMTS FP dissector flaws allowed out-of-bounds writes and crashes
Vulnerability Disclosure · 3 sources · Updated 3mo ago · First seen Jul 10, 2026

Wireshark disclosed and fixed memory-safety flaws in its UMTS FP dissector that could be triggered by malformed network traffic or crafted packet capture files opened in Wireshark, tshark, or sharkd. One issue, tracked as CVE-2026-15169 and published as wnpa-sec-2026-59, stems from dissect_e_dch_t2_or_common_channel_info() writing past a static subframes[16] array in the UMTS FP E-DCH Type-2 parser, enabling memory corruption and at minimum a reliable denial of service. Wireshark said the bug affects versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16, and was fixed in 4.6.7 and 4.4.17.
A related flaw in the same function was later assigned CVE-2026-76889 after researchers showed that a packet-controlled continuation flag could keep MAC-is descriptor parsing running beyond 16 entries, causing fixed-array out-of-bounds writes to mac_is_lchid[pdu_no][16] and mac_is_length[pdu_no][16]. The bugs were reproduced with sanitizers against development and pre-release builds, and Wireshark closed the reports after merging fixes including !25692 for UMTS-FP limits checking and !25780 for the MAC-is descriptor handling issue. The disclosures indicate the vulnerabilities could be exploited through injected malformed packets or malicious trace files, although no public exploits were reported at disclosure time.


