Skip to main content
Mallory
← Back to News
widely-deployed-product-advisoryendpoint-software-vulnerabilityproof-of-concept-release

Wireshark Kerberos Dissector Flaw Lets Malformed Packets Crash Analysis Tools

Patch & Detection Intelligence · 2 sources · Updated 3mo ago · First seen Aug 21, 2026

Wireshark Kerberos Dissector Flaw Lets Malformed Packets Crash Analysis Tools

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.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Jul 29, 2026 – Aug 12, 2026
  1. Aug 12, 20263mo ago

    Wireshark publishes wnpa-sec-2026-78 and fixed versions

    On 2026-08-12, Wireshark published security notice wnpa-sec-2026-78 for a Kerberos protocol dissector crash affecting versions 4.6.0 through 4.6.7 and 4.4.0 through 4.4.17. The notice said the flaw was fixed in versions 4.6.8 and 4.4.18, credited researchers from Aisle Research, O2Lab, and TAMU, and stated that no exploits were known.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2026-78 Kerberos protocol dissector crash
  2. Jul 29, 20264mo ago

    Wireshark issue 21449 documents Kerberos dissector out-of-bounds read

    On 2026-07-29, Wireshark's GitLab issue 21449 documented a high-severity out-of-bounds read in Kerberos learned-key formatting that could crash instrumented Wireshark or TShark when processing crafted plaintext Kerberos credential data. The issue was validated with ASan, linked to malformed short EncryptionKey handling, and notes that fixes were merged and the issue later received CVE-2026-76924.

    Kerberos learned-key formatting reads past short EncryptionKey (#21449) · Issue · wireshark/wireshark
Linked entities

Related entities

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.

Open in app →

Affected products

1 linked
Wireshark

Organizations

1 linked
Wireshark Foundation

Observables

5 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.