Loading story…
Wireshark disclosed CVE-2024-9781, a denial-of-service flaw in its AppleTalk and RELOAD Framing dissectors. Malformed network packets or specially crafted packet-capture files can cause Wireshark to crash during parsing; an attacker could potentially trigger the condition by injecting malformed traffic onto a monitored network, while analysts may be affected when opening a malicious capture file.
The issue was identified through internal fuzz testing, including the fuzz-2024-10-08-7201.pcap crash case, and Wireshark reported no known exploitation at disclosure. Affected releases are Wireshark 4.2.0 through 4.2.7 and 4.4.0; organizations should upgrade to 4.2.8 or 4.4.1, which contain the fix.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
Wireshark disclosed CVE-2024-9781, a denial-of-service flaw in its AppleTalk and RELOAD Framing dissectors that can crash the application when processing malformed network packets or capture files. The issue, found through internal testing with no known exploitation, affected versions 4.2.0 through 4.2.7 and 4.4.0 and was fixed in 4.2.8 and 4.4.1.
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-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 a denial-of-service vulnerability in its BEEP protocol dissector that can crash the packet analyzer through a stack-call overflow caused by recursive function handling. The issue is tracked as **CVE-2026-6538** and documented in advisory **`wnpa-sec-2026-23`**, with the underlying bug reported in Wireshark's issue tracker as a BEEP dissector stack-call overflow. The flaw affects Wireshark versions **4.6.0 through 4.6.4** and **4.4.0 through 4.4.14**. According to the vendor, an attacker could trigger the crash by injecting a malformed packet onto the network or by convincing a user to open a crafted capture file. Wireshark said no active exploits are known, credited Sharon Brizinov with discovery, and released fixes in versions **4.6.5** and **4.4.15**.
Aug 21, 2026
Wireshark disclosed **CVE-2025-1492**, a denial-of-service flaw that can crash the application through its Bundle Protocol and CBOR dissectors. The issue, identified through OSS-Fuzz, affects Wireshark versions `4.4.0`–`4.4.3` and `4.2.0`–`4.2.10`; related fuzzing identified a stack-overflow condition while processing UDP protocol input. An attacker could trigger the crash by injecting a malformed packet onto a monitored network or by convincing a user to open a crafted packet-capture file. Wireshark reported no known exploitation and released fixes in versions `4.4.4` and `4.2.11`; organizations should upgrade affected installations or later versions.
Sep 23, 2026