Loading story…
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.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
Wireshark published security advisory wnpa-sec-2025-06 disclosing CVE-2025-13499, a Kafka dissector crash affecting version 4.6.0 and versions 4.4.0 through 4.4.10. The advisory said no exploits were known and directed users to upgrade to 4.6.1, 4.4.11, or later.
A later update on the Wireshark GitLab issue stated that the crash had been assigned CVE-2025-13499. This linked the previously tracked fuzzing issue to the published vulnerability identifier.
Wireshark resolved the Kafka dissector crash through merge request !22037 and commit 49137f8c, with related merge requests !22047 and !22048 carrying the same fix. The issue was marked done and closed in the project's GitLab tracker.
Wireshark's internal testing identified a crash in the Kafka dissector when tshark processed a crafted capture file on the release-4.4 branch. Developer analysis traced the fault to decompress_snappy returning success without initializing the decompressed tvbuff pointer in an Xerial framing edge case.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map 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 **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**.
Aug 21, 2026
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 **CVE-2026-5653**, a heap-based buffer overflow in its DCP-ETSI protocol dissector that can crash the network protocol analyzer and cause a denial of service. The flaw affects Wireshark versions `4.6.0` through `4.6.4` and `4.4.0` through `4.4.14`, and was assigned **CWE-122** with a **CVSS v3.1 score of 5.5**. According to the advisory, an attacker could trigger the issue by injecting a malformed packet onto the network or by convincing a user to open a crafted packet capture file. Wireshark fixed the vulnerability in versions `4.6.5` and `4.4.15`; the issue was discovered by Alexandre de Oliveira, and the vendor said no active exploits were known at the time of disclosure.
Aug 21, 2026