Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-5653: Heap-Based Buffer Overflow in Wireshark DCP-ETSI PFT Dissector

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.
CVSS7.5High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-5653CWE-122 · Heap-based Buffer Overflow

CVE-2026-5653 is a heap-based buffer overflow in Wireshark's DCP-ETSI PFT dissector, specifically in the Reed-Solomon forward-error-correction processing path. During fragment reassembly, the decoder processes fixed 255-byte blocks although the destination heap buffer can be allocated to a smaller size derived from fragment parameters. A crafted DCP-ETSI PFT packet sequence or capture file can therefore cause an out-of-bounds heap write and crash Wireshark. Affected versions are Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14.

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 causes Wireshark to crash, resulting in denial of service. The reported heap overflow can write attacker-controlled data beyond the allocated heap buffer; however, the available information establishes denial of service and does not establish code execution.

Mitigation

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

Until patched, avoid opening untrusted packet-capture files and reduce exposure to untrusted traffic that can be injected into live captures. Do not rely on these measures as a substitute for upgrading.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.6.5 or later for the 4.6.x release branch, or to version 4.4.15 or later for the 4.4.x release branch.

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-5653 exploited in the wild?
As of Oct 2, 2026, Mallory has no reports of CVE-2026-5653 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5653?
Yes. As of Oct 2, 2026, Mallory has reports of a public exploit for CVE-2026-5653.
Is there a patch for CVE-2026-5653?
Upgrade Wireshark to version 4.6.5 or later for the 4.6.x release branch, or to version 4.4.15 or later for the 4.4.x release branch.
What products are affected by CVE-2026-5653?
Wireshark Foundation Wireshark.
How severe is CVE-2026-5653?
CVE-2026-5653 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.21% (11th percentile) as of Oct 2, 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 activity1Community discussion across Reddit, Mastodon, and other social sources.