Loading story…
Wireshark disclosed a CMS protocol dissector vulnerability, tracked as CVE-2026-76881, that could crash Wireshark or TShark when processing malformed CMS SignedData. The bug was caused by CMS MessageDigest verification passing a missing digest AlgorithmIdentifier into strcmp() without a null check, creating a deterministic null pointer dereference during packet dissection. An attacker could trigger the crash by injecting a malformed packet onto the network or by convincing a user to open a crafted packet capture file.
The issue affected Wireshark 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. Wireshark said the remediation adds a guard so missing algorithms are marked as "[unable to verify]" instead of causing a crash, though the original report noted a remaining limitation involving shared last-algorithm state across nested or consecutive decodes. The flaw was reported by researchers from Aisle Research, O2Lab, and Texas A&M University, and Wireshark said no active exploits were known at disclosure time.
See real exploitation activity before you spend the cycle.
3 events from the most recent confirmed update back to the earliest known activity.
Wireshark published security notice wnpa-sec-2026-76 for the CMS protocol dissector crash, stating that versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.17 were affected and that fixes were available in 4.6.8 and 4.4.18. The advisory credited Aisle Research and named the discoverers, while noting that no exploits were known.
Wireshark merged remediation changes titled "CMS: Check if Digest Algorithm is NULL," adding a null guard so missing algorithms are marked as "[unable to verify]" instead of causing a crash. The issue was then closed by John Thacker with commit 02dd1e7a.
AISLE Research reported a medium-severity null pointer dereference in Wireshark's CMS MessageDigest verification logic that could deterministically crash Wireshark or TShark when dissecting a malformed SignedData structure. The issue was tracked in Wireshark as issue 21446 and later assigned CVE-2026-76881.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
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.
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-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
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 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