Loading story…
Wireshark released version 4.6.8 with fixes for a large set of security vulnerabilities spanning packet dissectors, codecs, parsers, and related utilities. The advisory tracks issues under wnpa-sec-2026-08 through wnpa-sec-2026-50 and describes widespread crash conditions, infinite loops that can trigger denial of service, and several flaws marked as possible code execution, including issues in the TLS dissector, RDP dissector, SBC codec, and profile import functionality. Affected components also include handlers for protocols such as SMB2, HTTP, WebSocket, ZigBee, MySQL, ICMPv6, and OpenFlow, highlighting risk across Wireshark’s packet parsing and decompression surface.
Supporting issue reports show specific parser weaknesses such as a BT-DHT dissector stack overflow via nested structs and an FC-SWILS dissector stack overflow via nested zone set objects, while CVE tracking includes identifiers such as CVE-2026-5408 and CVE-2026-5409. The release notes also reference additional non-CVE defects involving memory corruption, integer underflow, heap overflow, parser overflows, and stability problems in Sharkd, underscoring that malformed capture data or imported content could crash analysis workflows and, in some cases, potentially lead to code execution.
See real exploitation activity before you spend the cycle.
5 events from the most recent confirmed update back to the earliest known activity.
A new CVE entry disclosed CVE-2026-76886, a heap-based buffer overflow / denial-of-service flaw in Wireshark's C12.22 protocol dissector affecting versions before 4.6.8 and 4.4.18. The record references Wireshark advisory wnpa-sec-2026-75 and GitLab work item 21439.
Wireshark published advisory wnpa-sec-2026-08 for CVE-2026-5409, a crash vulnerability in the Monero dissector affecting versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. The issue could be triggered by a malformed packet or packet trace file and was fixed in versions 4.6.5 and 4.4.15.
A GitLab issue was opened to track an FC-SWILS dissector stack overflow via nested zone set objects, corresponding to CVE-2026-5406. The Wireshark advisory identified the issue as a crash-causing vulnerability.
A GitLab issue was opened to track a BT-DHT dissector stack overflow via nested structs, corresponding to CVE-2026-5408. The flaw was described in the Wireshark advisory as causing a crash.
Wireshark published release notes for version 4.6.8 that disclosed a large batch of vulnerabilities tracked as wnpa-sec-2026-08 through wnpa-sec-2026-50. The issues affected numerous dissectors, codecs, parsers, and utilities, including crashes, infinite loops, and several possible code execution flaws.
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.
10 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourceheise.de
Open sourceisc.sans.edu
Open sourcewireshark.org
Open sourcegitlab.com
Open sourcegitlab.com
Open sourcegitlab.com
Open sourcewireshark.org
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 and patched a broad set of vulnerabilities across its packet analysis engine, protocol dissectors, codecs, decompression routines, and the `sharkd` backend, with the most serious issues including possible code execution, memory corruption, and denial of service. The release notes for **Wireshark 4.6.6** aggregate advisories `wnpa-sec-2026-08` through `wnpa-sec-2026-50`, while earlier coordinated fixes shipped in **4.6.5** and **4.4.15** for affected `4.6.0-4.6.4` and `4.4.0-4.4.14` branches. One high-severity flaw, tracked as **CVE-2026-5656**, allowed a crafted configuration-profile ZIP to escape the intended extraction path and plant a Lua plugin for execution on the next launch. Additional issues included crashes and memory-safety bugs in AMR-NB (`CVE-2026-5654`), iLBC (`CVE-2026-5657`), ASN.1 PER (`CVE-2026-6527`), DCP-ETSI (`CVE-2026-5653`, `CVE-2026-6530`), and later `sharkd` and Bluetooth AVRCP flaws that could crash the process or potentially enable control-flow hijack. Several vulnerabilities were reachable simply by opening a malicious packet capture or by parsing malformed traffic on the wire. Wireshark documented infinite-loop and CPU-exhaustion conditions in the USB HID dissector (**CVE-2026-6534**), OpenFlow v5 dissector (**CVE-2026-6521**), and LZ77 decompression path (**CVE-2026-6533**), alongside crashes in BEEP (**CVE-2026-6538**) and other protocol handlers. GitLab issue reports show researchers and fuzzing jobs repeatedly triggering heap overflows, double-free conditions, NULL dereferences, and non-advancing-offset parser failures in components such as DCP-ETSI, H.245, MIH, eDonkey, and `sharkd`, underscoring that malformed captures can destabilize both the GUI and `tshark`. Wireshark said it was not aware of active exploitation at disclosure time and urged users to update to the fixed releases.
Aug 21, 2026
The Wireshark Foundation released **Wireshark 4.6.8** to fix **28 security vulnerabilities** that can crash the protocol analyzer during packet analysis, with issues tracked as `wnpa-sec-2026-64` through `wnpa-sec-2026-91`. The flaws affect multiple protocol dissectors, `sharkd`, the reassembly engine, and numerous capture-file parsers, and several can be triggered simply by opening **crafted saved capture files** rather than processing live traffic. One advisory affecting the **X.509IF dissector** (`wnpa-sec-2026-87`) is still awaiting a CVE identifier. The update also addresses additional memory-safety and stability problems outside the numbered advisory set, including a **stack buffer overflow** in the **K12/RF5 writer**, an **out-of-bounds read** in the **BLF writer**, a **NULL-pointer dereference** in **KNXIP Secure Wrapper** decryption, and **stack exhaustion** in the **NetLog JSON parser**. Wireshark 4.6.8 further corrects eight non-crashing **5G decoding errors** that displayed incorrect values, alongside operational fixes such as extcap path handling on UNIX-like systems and stability improvements on Windows, underscoring that offline packet-capture handling remains a meaningful attack surface for defenders and analysts.
Aug 21, 2026
Wireshark released version **4.6.5** to remediate more than 40 vulnerabilities, including multiple flaws that could allow **arbitrary code execution** when the tool processes malformed network packets or malicious capture and profile files. The most severe issues were reported in the **TLS dissector**, **SBC codec**, **RDP dissector**, and **profile import** functionality, where crashes may be exploitable for code execution. The release also fixes a broad set of **denial-of-service** bugs across numerous protocol dissectors, several **infinite-loop** conditions that can stall unattended analysis workflows, and decompression-related crashes in **zlib** and **LZ77** handling. Because Wireshark is widely deployed in enterprise security operations, packet analysis, and SIEM-connected environments—sometimes with elevated privileges—the patched version is being treated as a high-priority security update.
Jun 29, 2026