Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-15166: Stack-based buffer overflow in Wireshark IEEE 802.11 EAPOL-Key decryption

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
CVSS5.5Medium · v3.1
EPSS0.14%3rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-15166CWE-121 · Stack-based Buffer Overflow

CVE-2026-15166 is a stack-based buffer overflow in Wireshark's IEEE 802.11 decryption handling, affecting versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16. Dot11DecryptDecryptKeyData() copies EAPOL-Key data into a fixed 1024-byte stack buffer allocated by try_decrypt_keydata(). In the RC4/TKIP branch, the attacker-controlled key_bytes_len is checked against the EAPOL frame length but not against the destination buffer capacity. A crafted EAPOL-Key frame can therefore cause an out-of-bounds stack write when processed with WPA decryption enabled and a valid security association established. The vulnerability 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 corrupts stack memory and can terminate the analyzing Wireshark or tshark process, interrupting packet analysis. A reproducer demonstrated a 2000-byte write into a 1024-byte stack buffer. Arbitrary code execution is a potential consequence of the memory corruption, but successful code execution has not been established; denial of service is the confirmed impact.

Mitigation

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

Until patched, avoid opening untrusted packet captures or analyzing untrusted IEEE 802.11 traffic with affected versions. Disable WPA decryption to prevent reaching the documented vulnerable decryption path, or disable IEEE 802.11 dissection where operationally feasible. Restrict analysis to trusted capture sources.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.6.7 or later in the 4.6 branch, or 4.4.17 or later in the 4.4 branch. Update tshark and associated Wireshark libraries as applicable. Distribution-managed installations should install the vendor's fixed packages, which may contain backported fixes; Debian 13 provides fixes in version 4.4.18-0+deb13u1. The code-level fix rejects oversized EAPOL values before copying data into the fixed-size destination buffer.

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-15166 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-15166 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15166?
Yes. As of Nov 6, 2026, Mallory has reports of a public exploit for CVE-2026-15166.
Is there a patch for CVE-2026-15166?
Upgrade Wireshark to version 4.6.7 or later in the 4.6 branch, or 4.4.17 or later in the 4.4 branch. Update tshark and associated Wireshark libraries as applicable.
What products are affected by CVE-2026-15166?
Wireshark Foundation Wireshark.
How severe is CVE-2026-15166?
CVE-2026-15166 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.14% (3rd percentile) as of Nov 6, 2026.
Activity feed

Recent activity

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

View more in app →
+7 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.