CVE-2026-5402: Wireshark TLS ECH Transcript Reconstruction Heap Buffer Overflow
- Vendor
- Wireshark Foundation
CVE-2026-5402 is a heap-based buffer overflow in the Wireshark TLS dissector's Encrypted Client Hello (ECH) transcript-reconstruction logic. Integer truncation in the ech_outer_extensions processing loop causes incorrect buffer-boundary calculations and permits attacker-controlled data to be written beyond a heap allocation. The issue affects Wireshark 4.6.0 through 4.6.4 and 4.7.0rc0 on all platforms. Wireshark 4.4.x and earlier are unaffected because they do not include the vulnerable ECH decryption code path. The flaw is primarily classified as CWE-122 and also involves numeric truncation and integer-to-buffer-overflow conditions.
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.
A successful trigger can crash Wireshark, causing denial of service. Because the overflow writes attacker-controlled bytes past a heap buffer, exploitation may also permit code execution in the security context of the Wireshark process. This particularly affects analysts processing untrusted traffic or capture data and may have greater consequence where Wireshark is operated with elevated privileges.
Mitigation
If you can’t patch tonight, do this now.
Until upgrading, avoid opening untrusted capture files and avoid directly dissecting untrusted live traffic in vulnerable versions. Perform analysis in an isolated, least-privileged environment. Where operationally viable, use an unaffected Wireshark 4.4.x release as a temporary workaround, since that branch lacks the vulnerable ECH decryption path.
Remediation
Patch, then assume compromise.
Upgrade to Wireshark 4.6.5 or later. The remediation replaces unsafe narrow integer handling with wider types and improves ClientHello bounds handling by constraining parsing to an appropriate subset buffer before length validation and transcript reconstruction.
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.
References
Frequently asked questions
- Is CVE-2026-5402 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-5402 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-5402?
- Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-5402.
- Is there a patch for CVE-2026-5402?
- Upgrade to Wireshark 4.6.5 or later. The remediation replaces unsafe narrow integer handling with wider types and improves ClientHello bounds handling by constraining parsing to an appropriate subset buffer before length validation and transcript reconstruction.
- What products are affected by CVE-2026-5402?
- Wireshark Foundation Wireshark.
- How severe is CVE-2026-5402?
- CVE-2026-5402 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.39% (34th percentile) as of Sep 25, 2026.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.