Loading story…
Wireshark disclosed CVE-2026-15171, a denial-of-service flaw in the SSH protocol dissector that can crash the application when a user opens a specially crafted pcapng trace file. The bug stems from a NULL pointer dereference in ssh_keylog_process_line() while parsing a malformed SSH Decryption Secrets Block, where empty or oversized hex tokens can cause ssh_kex_make_bignum() to return NULL and then be dereferenced.
The issue affects workflows that process untrusted capture files with embedded SSH decryption metadata, including the Wireshark GUI, tshark, and sharkd, but it is not triggered by malicious SSH network traffic alone because the attacker-controlled input must be in pcapng metadata. Wireshark said the flaw affects versions 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16, with fixes released in 4.6.7 and 4.4.17; the bug was reproduced with AddressSanitizer via OSS-Fuzz, and no active exploits were known at disclosure time.
See real exploitation activity before you spend the cycle.
4 events from the most recent confirmed update back to the earliest known activity.
Wireshark stated that CVE-2026-15171 was fixed in versions 4.6.7 and 4.4.17, with affected ranges listed as 4.6.0 through 4.6.6 and 4.4.0 through 4.4.16. Users were advised to upgrade to the fixed releases or later.
On July 8, 2026, Wireshark published security advisory wnpa-sec-2026-55 for CVE-2026-15171, describing an SSH protocol dissector crash that could be triggered by persuading a user to open a malformed packet trace file. The advisory credited Aisle Research and stated that no exploits were known.
Aisle Research reported that Wireshark could crash with a NULL pointer dereference in `ssh_keylog_process_line()` when opening a crafted pcapng file containing malformed SSH Decryption Secrets metadata. The issue affected workflows such as the Wireshark GUI, `tshark`, and `sharkd`, and was characterized as a denial-of-service condition rather than remote code execution.
Wireshark merged fix-related merge requests `!25557`, `!25561`, and `!25562`, and the issue activity states the bug was closed with commit `97421ea7`. The project also assigned CVE-2026-15171 to the vulnerability.
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 real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
wireshark.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 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-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 **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