Loading story…
Wireshark disclosed CVE-2024-11596, a denial-of-service flaw in its ECMP dissector that can crash Wireshark or the command-line tshark utility when they process malformed ECMP traffic. An attacker could trigger the condition by injecting crafted packets onto a monitored network or persuading an analyst or automated processing system to open a malicious packet-capture file; testing showed tshark terminating with a buffer-overflow detection error.
The affected releases are Wireshark 4.4.0 through 4.4.1 and 4.2.0 through 4.2.8. Wireshark corrected the string-buffer arithmetic defect in versions 4.4.2 and 4.2.9; disabling ECMP dissection also prevented the observed crash. No exploitation was known when the advisory was issued.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
Wireshark merged merge requests !18074, !18075, and !18076 to resolve an ECMP dissector flaw triggered by a crafted packet capture; the GitLab issue was closed by John Thacker. The changes were titled “ECMP: Exorcise a string buffer arithmetic gremlin.”
The Wireshark ECMP dissector vulnerability was assigned CVE-2024-11596.
Wireshark published advisory wnpa-sec-2024-15 for an ECMP dissector vulnerability that can crash the application when it processes malformed network packets or packet-capture files. The advisory identified affected versions 4.4.0–4.4.1 and 4.2.0–4.2.8, stated no exploitation was known, and said the issue was fixed in versions 4.4.2 and 4.2.9.
Sake Blok referenced commits 8fd60c64 and 06e0b0bb in connection with the ECMP dissector issue.
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-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
Wireshark disclosed **CVE-2025-5601**, a denial-of-service flaw in its dissection engine’s column utility handling. A remote attacker could inject a malformed packet onto a monitored network, or trick an analyst into opening a crafted capture file, to crash Wireshark or TShark. The affected releases are Wireshark `4.4.0`–`4.4.6` and `4.2.0`–`4.2.11`; Wireshark reported no known exploitation and said the issue was identified through internal testing. Fuzzing of a crafted PCAP uncovered an out-of-bounds heap write in CLNP dissection paths that invoked column-handling functions, corrupting heap metadata and causing Valgrind to abort. The remediation constrains column-fence handling during prepending so it cannot exceed the column size. Wireshark’s advisory identifies `4.2.12` and `4.4.7` as fixed releases, while the associated development issue was subsequently retargeted to `4.4.8`, so organizations should deploy the latest supported Wireshark maintenance release.
Sep 23, 2026
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