CVE-2026-76889: Wireshark UMTS FP Dissector Out-of-Bounds Write
- Vendor
- Wireshark Foundation
CVE-2026-76889 is an out-of-bounds write vulnerability in the Wireshark UMTS FP protocol dissector affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18. The function dissect_e_dch_t2_or_common_channel_info() fails to bound the MAC-is SDU descriptor count before using it to index two fixed 16-element arrays, mac_is_lchid and mac_is_length. A crafted descriptor sequence with the packet-controlled F continuation flag kept clear allows the loop to advance beyond index 15 and write outside these arrays. The loop continues consuming input, so the dissector idleness check does not prevent the invalid writes. Processing a malicious capture can crash Wireshark or TShark, causing denial of service.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can crash the analyzing process and interrupt packet analysis or workflows dependent on it. The demonstrated memory-safety violation is an out-of-bounds write. Arbitrary code execution, confidentiality loss, and integrity compromise have not been established for this specific CVE.
Mitigation
If you can’t patch tonight, do this now.
Until a fixed package is installed, avoid processing untrusted captures containing UMTS FP traffic. Where operationally feasible, disable the UMTS FP dissector to prevent the affected parsing path from being reached. These measures do not replace the security update.
Remediation
Patch, then assume compromise.
Install a vendor-supported Wireshark update explicitly fixing CVE-2026-76889. For upstream installations, use a fixed release newer than 4.6.7 or 4.4.18 in the respective branch. Debian 13 provides the fix in version 4.4.18-0+deb13u1. Distribution packages may contain backported fixes despite retaining an otherwise affected upstream version. The code-level fix must validate descriptor counts against the 16-element array bounds before writing; the issue was closed following merge request !25780, which added UMTS FP bounds checking.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-76889 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2026-76889 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-76889?
- Yes. As of Nov 4, 2026, Mallory has reports of a public exploit for CVE-2026-76889.
- Is there a patch for CVE-2026-76889?
- Install a vendor-supported Wireshark update explicitly fixing CVE-2026-76889. For upstream installations, use a fixed release newer than 4.6.7 or 4.4.18 in the respective branch.
- What products are affected by CVE-2026-76889?
- Wireshark Foundation Wireshark.
- How severe is CVE-2026-76889?
- CVE-2026-76889 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Nov 4, 2026.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.