Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-6532: Kismet Dissector Heap Buffer Over-read in Wireshark

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.
CVSS5.5Medium · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-6532CWE-126 · Buffer Over-read

CVE-2026-6532 is a heap buffer over-read in Wireshark's Kismet protocol dissector. Processing malformed Kismet packet data can reach the text-formatting path and perform an out-of-bounds read, causing Wireshark or tshark to crash. Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14 are affected.

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 cause a denial of service by crashing Wireshark or tshark. This can interrupt interactive packet analysis and automated packet-processing workflows.

Mitigation

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

Until upgrades are deployed, avoid analyzing untrusted packet-trace files and limit exposure to untrusted network traffic, particularly on interfaces used for live capture. Run Wireshark and tshark with least privilege where operationally feasible.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.6.5 or later on the 4.6 branch, or to version 4.4.15 or later on the 4.4 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-6532 exploited in the wild?
As of Oct 2, 2026, Mallory has no reports of CVE-2026-6532 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6532?
Yes. As of Oct 2, 2026, Mallory has reports of a public exploit for CVE-2026-6532.
Is there a patch for CVE-2026-6532?
Upgrade Wireshark to version 4.6.5 or later on the 4.6 branch, or to version 4.4.15 or later on the 4.4 branch.
What products are affected by CVE-2026-6532?
Wireshark Foundation Wireshark.
How severe is CVE-2026-6532?
CVE-2026-6532 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.19% (9th 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.