Loading story…
Wireshark disclosed CVE-2026-3203, a crash vulnerability in its RF4CE Profile dissector that can be triggered by malformed RF4CE/ZigBee traffic or a crafted packet capture file. The issue was uncovered during internal fuzz testing, which found that tshark on the release-4.6 branch could hit a segmentation fault while processing a crafted capture derived from an RF4CE example file. AddressSanitizer traced the invalid read to RF4CE and ZigBee decryption code, including zbee_sec_ccm_decrypt in packet-zbee-security.c and related RF4CE dissector paths.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Wireshark dated security notice wnpa-sec-2026-07 for an RF4CE Profile dissector crash identified as CVE-2026-3203. The notice said the flaw affected versions 4.6.0 through 4.6.3 and 4.4.0 through 4.4.13, and that no exploits were known.
An automated Wireshark fuzzing job on the release-4.6 branch found a segmentation fault when tshark processed a crafted capture file, with the crash traced through RF4CE/ZigBee decryption code. The issue was tracked as GitLab issue #21009 and later associated with CVE-2026-3203.
Wireshark stated the RF4CE Profile dissector crash was fixed in versions 4.6.4 and 4.4.14, and advised users to upgrade. The GitLab issue also links the fix to merged changes titled "RF4CE: Check that the input data is long enough."
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.
3 references tracked. Mallory keeps watching after this page renders.
wireshark.org
Open sourcecve.mitre.org
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 **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 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-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.
Sep 23, 2026