Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisory

Wireshark Kismet dissector flaw lets malformed packets crash tshark and Wireshark

Vulnerability Disclosure · 4 sources · Updated 3mo ago · First seen Apr 30, 2026

Wireshark Kismet dissector flaw lets malformed packets crash tshark and Wireshark

Wireshark disclosed CVE-2026-6532, a crash-causing flaw in the Kismet protocol dissector that can be triggered by a malformed packet on the network or by opening a crafted packet capture file. The issue affects Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14, and has been fixed in 4.6.5 and 4.4.15. Wireshark said no exploits are known and credited Sharon Brizinov with discovering the vulnerability.

A related fuzzing report showed a heap-buffer-overflow in tshark while processing a crafted capture, with the crash occurring in format_text_internal and being reached through packet-kismet.c during packet dissection. The bug was reproduced in Wireshark's CI fuzzing environment on Ubuntu 24.04.4 LTS, and the original crash report was later marked as a duplicate of a dedicated Kismet dissector issue and explicitly assigned CVE-2026-6532.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Mar 30, 2026 – Apr 30, 2026
  1. Apr 30, 20267mo ago

    CVE-2026-6532 record is published

    A CVE record for CVE-2026-6532 was published, formally tracking the Wireshark Kismet dissector crash vulnerability. The record corresponds to the issue later referenced by Wireshark's advisory.

    CVE Record: CVE-2026-6532
  2. Apr 29, 20267mo ago

    Wireshark publishes advisory and fixes for CVE-2026-6532

    Wireshark published advisory WNPA-SEC-2026-29 for CVE-2026-6532, describing a crash in the Kismet protocol dissector that affects versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. The company said the issue was fixed in versions 4.6.5 and 4.4.15 and noted no known exploits at publication time.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2026-29 Kismet protocol dissector crash
  3. Mar 30, 20268mo ago

    Wireshark fuzzing job detects Kismet dissector heap-buffer-overflow

    A Wireshark ASan Menagerie Fuzz CI job found a heap-buffer-overflow in tshark while processing a crafted capture through the Kismet dissector. The crash occurred on the master branch and was traced to an out-of-bounds read in format_text_internal reached via packet-kismet.c.

    Fuzz job crash: fuzz-2026-03-30-13710906068.pcap (#21128) · Issue · wireshark/wireshark
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

1 linked
Wireshark

Organizations

1 linked
Wireshark Foundation

Observables

5 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.