Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-15169: Out-of-bounds write in Wireshark UMTS FP dissector

Published Jul 8, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 1 in a dayToday
CVSS7.5High · v3.1
EPSS0.27%20th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-15169CWE-787

CVE-2026-15169 is an out-of-bounds write in the Wireshark UMTS FP E-DCH Type-2 dissector, affecting versions 4.6.0–4.6.6 and 4.4.0–4.4.16. In dissect_e_dch_t2_or_common_channel_info(), a packet-controlled descriptor loop increments a MAC-is SDU index without enforcing the 16-entry bounds of the destination arrays. Malformed descriptors can therefore cause attacker-controlled logical-channel identifiers and lengths to overwrite adjacent static or global memory. An in-loop diagnostic does not stop processing, and a subsequent assertion checks an inappropriate limit after the writes have occurred. Processing a crafted packet or packet trace can crash the application and cause 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 corrupts memory and can reliably crash Wireshark or affected tshark and sharkd processes, interrupting packet capture analysis or automated processing. Arbitrary code execution and confidentiality compromise have not been established for this CVE.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid opening untrusted packet traces and restrict capture exposure to attacker-controlled traffic. Where operationally feasible, disable UMTS FP dissection to prevent the vulnerable parsing path from being invoked. These measures reduce exposure but do not replace the security update.

Remediation

Patch, then assume compromise.

Upgrade Wireshark and associated components to version 4.6.7 or later on the 4.6 branch, or 4.4.17 or later on the 4.4 branch. Distribution-managed installations should apply the vendor's fixed packages; identified updates include Debian 13 version 4.4.18-0+deb13u1 and Alpine version 4.6.9-r0. The underlying code correction requires enforcing array bounds and validating MAC-is SDU counts before performing stores.

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-15169 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-15169 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15169?
Yes. As of Nov 6, 2026, Mallory has reports of a public exploit for CVE-2026-15169.
Is there a patch for CVE-2026-15169?
Upgrade Wireshark and associated components to version 4.6.7 or later on the 4.6 branch, or 4.4.17 or later on the 4.4 branch. Distribution-managed installations should apply the vendor's fixed packages; identified updates include Debian 13 version 4.4.18-0+deb13u1 and Alpine version 4.6.9-r0.
What products are affected by CVE-2026-15169?
Wireshark Foundation Wireshark.
How severe is CVE-2026-15169?
CVE-2026-15169 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.27% (20th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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.