Wireshark Kerberos Dissector Flaw Lets Malformed Packets Crash Analysis Tools
Patch & Detection Intelligence · 2 sources · Updated 3mo ago · First seen 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.


