Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-5402: Wireshark TLS ECH Transcript Reconstruction Heap Buffer Overflow

Published Apr 30, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.39%34th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-5402CWE-122 · Heap-based Buffer Overflow

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.

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.

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.

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-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.
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 activity6Community discussion across Reddit, Mastodon, and other social sources.