Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-76889: Wireshark UMTS FP Dissector Out-of-Bounds Write

Published Aug 19, 2026 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.5Medium · v3.1
EPSS0.13%3rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-76889CWE-787

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Wireshark FoundationWiresharkapplication
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.