CVE-2026-15166: Stack-based buffer overflow in Wireshark IEEE 802.11 EAPOL-Key decryption
- Vendor
- Wireshark Foundation
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.
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.
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-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.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.