Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-15165: Heap buffer overflow in Wireshark TLS ECH 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-15165CWE-122 · Heap-based Buffer Overflow

CVE-2026-15165 is a heap-based buffer overflow in TLS Encrypted Client Hello (ECH) decryption affecting Wireshark and tshark versions 4.6.0 through 4.6.6. The ssl_dissect_hnd_hello_ext_ech() function allocates a reconstructed transcript buffer based on the outer ClientHello length, then copies referenced outer extensions without checking destination capacity. Repeated ech_outer_extensions entries can cause the same large outer extension to be copied multiple times, exceeding the allocation. The implementation also fails to enforce the requirement that at most one ech_outer_extensions extension be present. Processing a crafted packet capture can corrupt heap memory and crash the application. Wireshark 4.6.7 fixes the vulnerability.

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 crafted packet capture can cause attacker-controlled out-of-bounds heap writes and terminate Wireshark or tshark, disrupting interactive analysis or automated capture-processing workflows. Testing observed 4,100-byte writes per copy and approximately 328 KB of total overflow. Code execution is a potential consequence of the memory corruption, but it has not been demonstrated for this vulnerability; the confirmed impact is denial of service.

Mitigation

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

Until patched, avoid opening or processing untrusted packet captures with affected Wireshark or tshark versions, including through automated analysis workflows.

Remediation

Patch, then assume compromise.

Upgrade Wireshark and tshark to version 4.6.7 or later, or install the corresponding distribution security update. Alpine Linux users can update the affected packages to 4.6.9-r0 or later. Photon OS 5.0 users should apply the Wireshark update associated with PHSA-2026-5.0-91-0986. Source-level remediation requires checking destination capacity before copying outer extensions and rejecting repeated ech_outer_extensions entries.

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-15165 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-15165 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15165?
Yes. As of Nov 6, 2026, Mallory has reports of a public exploit for CVE-2026-15165.
Is there a patch for CVE-2026-15165?
Upgrade Wireshark and tshark to version 4.6.7 or later, or install the corresponding distribution security update. Alpine Linux users can update the affected packages to 4.6.9-r0 or later.
What products are affected by CVE-2026-15165?
Wireshark Foundation Wireshark.
How severe is CVE-2026-15165?
CVE-2026-15165 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

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

View more in app →
+3 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 activity3Community discussion across Reddit, Mastodon, and other social sources.