CVE-2026-76924: Out-of-bounds read in Wireshark Kerberos learned-key formatting
- Vendor
- Wireshark Foundation
Wireshark 4.6.0–4.6.7 and 4.4.0–4.4.18 contain an out-of-bounds read in the Kerberos dissector's learned-key formatting logic. When recording an EncryptionKey, save_encryption_key copies the declared key bytes into retained storage but formats a four-byte preview directly from the original input buffer. Keys containing only one to three bytes can therefore cause reads beyond that buffer. A crafted plaintext EncKrbCredPart containing KrbCredInfo with a short EncryptionKey can trigger the flaw without successful decryption. BER reassembly of a constructed OCTET STRING into an exact-size allocation exposes the overread, which can crash Wireshark or TShark and cause denial of service.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Malformed Kerberos data can terminate the analyzing Wireshark or TShark process, interrupting packet inspection or automated analysis. A heap-buffer-overflow read was reproduced under AddressSanitizer. The default block allocator can mask the small overread, so termination is not necessarily deterministic across configurations. Arbitrary code execution and disclosure of memory contents are not established for this CVE.
Mitigation
If you can’t patch tonight, do this now.
Until patched, disable Kerberos protocol dissection where operationally acceptable and avoid analyzing untrusted Kerberos traffic or captures containing it. These measures reduce exposure to the vulnerable parsing path but do not correct the underlying out-of-bounds read.
Remediation
Patch, then assume compromise.
Install vendor-provided Wireshark security updates addressing CVE-2026-76924. Debian 13 fixes the issue in version 4.4.18-0+deb13u1. For other distributions, use the vendor's patched package rather than relying solely on the upstream version number. The code fix formats the four-byte preview from the zero-initialized retained key buffer after the bounded copy, rather than from the original short input buffer; it updates both the ASN.1 template and generated dissector code.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-76924 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2026-76924 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-76924?
- Yes. As of Nov 4, 2026, Mallory has reports of a public exploit for CVE-2026-76924.
- Is there a patch for CVE-2026-76924?
- Install vendor-provided Wireshark security updates addressing CVE-2026-76924. Debian 13 fixes the issue in version 4.4.18-0+deb13u1.
- What products are affected by CVE-2026-76924?
- Wireshark Foundation Wireshark.
- How severe is CVE-2026-76924?
- CVE-2026-76924 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.14% (3rd percentile) as of Nov 4, 2026.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.