Skip to main content
Mallory
MediumVulnerability

CVE-2025-13499: Kafka dissector crash in Wireshark

Published Nov 21, 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.
CVSS5.5Medium · v3.1
EPSS0.13%2nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2025-13499CWE-824 · Access of Uninitialized Pointer

CVE-2025-13499 is a denial-of-service vulnerability in the Wireshark Kafka dissector affecting Wireshark 4.6.0 and 4.4.0 through 4.4.10. Kafka Snappy decompression handling for an Xerial-framed payload with a length of 16 can report successful decompression without initializing the decompressed buffer pointer. Subsequent processing accesses that uninitialized pointer and triggers an assertion failure, crashing Wireshark or tshark when processing malformed Kafka traffic or a crafted packet-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.

An attacker can terminate a Wireshark or tshark process, causing denial of service. The available information does not indicate confidentiality loss, integrity loss, or code execution.

Mitigation

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

Until patched, do not open packet captures from untrusted sources in Wireshark or TShark, and limit the ability of untrusted parties to inject Kafka traffic into networks monitored by vulnerable Wireshark instances.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.6.1, 4.4.11, or a later release. The issue was fixed through changes to Kafka Snappy decompression handling.

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-13499 exploited in the wild?
As of Oct 2, 2026, Mallory has no reports of CVE-2025-13499 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-13499?
As of Oct 2, 2026, Mallory has found no public exploit for CVE-2025-13499.
Is there a patch for CVE-2025-13499?
Upgrade Wireshark to version 4.6.1, 4.4.11, or a later release. The issue was fixed through changes to Kafka Snappy decompression handling.
What products are affected by CVE-2025-13499?
Wireshark Foundation Wireshark.
How severe is CVE-2025-13499?
CVE-2025-13499 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.13% (2nd 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 activity2Community discussion across Reddit, Mastodon, and other social sources.