Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2025-5601: Wireshark Column Utility Out-of-Bounds Write Denial of Service

Published Jun 4, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS0.32%26th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2025-5601CWE-787 · Out-of-bounds Write

CVE-2025-5601 is an out-of-bounds heap-write flaw in Wireshark's column utility module that can crash dissectors during packet dissection. Processing a malformed packet can reach column-handling operations from the CLNP dissector, causing writes beyond an allocated heap block and heap-metadata corruption. Wireshark 4.4.0 through 4.4.6 and 4.2.0 through 4.2.11 are affected. The flaw can be triggered through malformed packet injection or by opening a crafted capture file.

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 can terminate Wireshark or TShark, causing denial of service. The observed failure corrupted heap metadata and caused Valgrind to abort; the documented impact is a dissection-engine crash.

Mitigation

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

Until upgraded, avoid opening untrusted packet-trace files and reduce the ability of untrusted parties to inject malformed packets into networks monitored by vulnerable Wireshark or TShark instances. No separate vendor workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.4.7 or later for the 4.4 release line, or to version 4.2.12 or later for the 4.2 release line. These versions contain the fixes for CVE-2025-5601.

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-2025-5601 exploited in the wild?
As of Oct 1, 2026, Mallory has no reports of CVE-2025-5601 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-5601?
Yes. As of Oct 1, 2026, Mallory has reports of a public exploit for CVE-2025-5601.
Is there a patch for CVE-2025-5601?
Upgrade Wireshark to version 4.4.7 or later for the 4.4 release line, or to version 4.2.12 or later for the 4.2 release line. These versions contain the fixes for CVE-2025-5601.
What products are affected by CVE-2025-5601?
Wireshark Foundation Wireshark.
How severe is CVE-2025-5601?
CVE-2025-5601 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.32% (26th percentile) as of Oct 1, 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 activity10Community discussion across Reddit, Mastodon, and other social sources.