Loading story…
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.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
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.
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.
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.
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.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cve.mitre.org
Open sourcewireshark.org
Open sourcegitlab.com
Open sourcegitlab.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Wireshark disclosed a high-severity flaw in its Kerberos protocol dissector that can crash **Wireshark** or **TShark** when processing malformed traffic or packet captures. The bug, tracked as `CVE-2026-76924` and documented in advisory `wnpa-sec-2026-78`, stems from an out-of-bounds read while formatting a preview of a learned `EncryptionKey` from plaintext Kerberos credential data. Researchers reported that a crafted `EncKrbCredPart`, including traffic delivered over UDP/88, could trigger a heap-buffer-overflow even without a valid keytab, valid key, or successful decryption. The vendor said the issue affects Wireshark versions **4.6.0 through 4.6.7** and **4.4.0 through 4.4.17**, and it has been fixed in **4.6.8** and **4.4.18**. The root cause was that the dissector copied bounded key bytes into retained storage but still read four bytes from the original input buffer, allowing one- to three-byte keys to cause the crash; the fix reformats the preview from a zero-initialized retained buffer after the bounded copy. Wireshark said malformed packets injected onto a network or malicious packet capture files could trigger the vulnerability, and no active exploits are known.
Aug 21, 2026
Wireshark disclosed a vulnerability in its Tektronix K12xx/`.rf5` file parser that can crash the packet analyzer when a user opens a specially crafted capture file. The issue, tracked as **CVE-2026-76885** and **wnpa-sec-2026-71**, stems from incorrect handling of skipped 16-byte blobs in `get_record()`, which can inflate the reported record length and lead downstream functions such as `k12_read()`, `k12_seek_read()`, and `process_packet_data()` to read past a heap buffer boundary. The bug was reported by Jaime Cavero and reproduced with AddressSanitizer in both `tshark` and `capinfos` using a synthetic malicious `.rf5` sample. Wireshark said the flaw affects versions **4.6.0 through 4.6.7** and **4.4.0 through 4.4.17**, and was fixed in **4.6.8** and **4.4.18** through merged K12 buffer-overrun patches; the project said no active exploits are known, but warned that an attacker could trigger a denial of service by convincing a target to open a malformed capture file.
Aug 21, 2026
Wireshark disclosed **CVE-2025-13499**, a denial-of-service flaw in its Kafka dissector that can crash the application when it processes malformed network traffic or a specially crafted packet capture file. The issue affects Wireshark `4.6.0` and `4.4.0` through `4.4.10`, and the project said no active exploits were known at disclosure. Users were advised to upgrade to **Wireshark 4.6.1, 4.4.11, or later**. Project details show the bug was uncovered by an internal fuzzing job on the `release-4.4` branch after `tshark` processed a crafted `.pcap` file and hit an assertion failure in `epan/tvbuff.c`. Developers traced the crash to Kafka Snappy decompression logic handling Xerial framing: when the length equaled `16`, the code returned success without initializing the decompressed `tvbuff` pointer, leaving `composite_tvb` unset and causing the crash. Wireshark fixed the flaw in merge request `!22037` and commit `49137f8c`.
Aug 21, 2026