Loading story…
Wireshark fixed CVE-2026-15173, a heap-buffer-overflow in the pcapng legacy Darwin Process Info Block (DPIB) UUID rewrite path. A malicious pcapng file containing an oversized OPT_DPIB_UUID option can cause Wireshark components to allocate 16 bytes for the UUID but copy the option's actual, larger length during packet-capture rewrite or export operations, resulting in memory corruption and a crash.
The flaw affects Wireshark versions 4.6.0 through 4.6.6 and is remediated in 4.6.7. Researchers reproduced it with 32-byte UUID-option files using editcap and tshark output writing; read-only packet inspection was not reported to trigger the vulnerable path. Wireshark reported no known exploitation as of its advisory and organizations should upgrade systems that process untrusted pcapng captures.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Wireshark published advisory WNPA-SEC-2026-53 for CVE-2026-15173, a denial-of-service crash issue affecting versions 4.6.0 through 4.6.6. Version 4.6.7 fixed the issue, and Wireshark stated that no exploits were known at the time of the advisory.
Wireshark merged merge request !25404, “wiretap: pcapng-darwin-custom: Don't overflow allocated option size,” and closed issue 21285 with commit 63aab2af. The issue was assigned CVE-2026-15173.
Mitchell Benjamin reported a heap-buffer-overflow in Wireshark's pcapng legacy Darwin Process Info Block UUID rewrite path. A malformed file with an oversized UUID option could trigger the allocation-and-copy mismatch when rewritten or exported through tools such as editcap or tshark.
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 and patched a high-severity vulnerability in its C12.22 protocol dissector that can crash the application when processing malformed traffic or packet captures. The flaw, tracked as **CVE-2026-76886** and covered by advisory **`wnpa-sec-2026-75`**, stems from the EAX/CMAC decryption path, where `Eax_Decrypt()` accepts 32-bit lengths but passes them into 16-bit CMAC helper logic, causing integer truncation, undersized heap allocation, and subsequent oversized `memcpy()` operations that lead to a heap-buffer overflow. The vulnerable code path is reachable through reassembled C12.22 traffic over **TCP/1153** when **`c1222.decrypt`** is enabled and a matching decryption-table entry exists; researchers reported that a crafted **65,576-byte** MESSAGE can reliably trigger the crash. Wireshark said affected versions are **4.6.0 through 4.6.7** and **4.4.0 through 4.4.17**, with fixes released in **4.6.8** and **4.4.18** that reject oversized CMAC inputs before allocation. The issue was reported by researchers from **Aisle Research, O2Lab, and TAMU**, and Wireshark said no active exploits are known.
Aug 21, 2026
Wireshark disclosed and patched multiple vulnerabilities in its Catapult DCT2000 handling code, including a protocol dissector crash tracked as **CVE-2026-15174** and a separate file parser flaw later assigned **CVE-2026-76883**. The first issue, published as advisory **`wnpa-sec-2026-52`**, affects Wireshark versions **4.6.0 through 4.6.6** and **4.4.0 through 4.4.16** and can be triggered by a malformed packet on the wire or by opening a malformed packet trace file, causing the application to crash. A later advisory, **`wnpa-sec-2026-74`**, covers a Catapult DCT2000 file parser crash affecting versions **4.6.0 through 4.6.7** and **4.4.0 through 4.4.17**, fixed in **4.6.8** and **4.4.18**. Separately, a GitLab issue detailed an off-by-one heap out-of-bounds write in `parse_line()` within `wiretap/catapult_dct2000.c`, where the parser allocates `floor(data_chars/2)` bytes but may write `ceil(data_chars/2)` bytes when the input length is odd; developers confirmed the bug, noted practical triggering requires exactly **2049 bytes**, and merged fixes. Wireshark said no exploits are known for the disclosed issues and advised users to upgrade to patched releases.
Aug 21, 2026