CVE-2026-76924 is an out-of-bounds read in Wireshark's Kerberos protocol dissector while it records a learned EncryptionKey from plaintext Kerberos credential data. The affected learned-key formatting logic performs a bounded copy into zero-initialized retained key storage, but formats a four-byte key preview from the original input buffer. An EncryptionKey containing only one to three bytes can therefore cause the formatter to read beyond the input allocation. The flaw affects Wireshark 4.6.0 through 4.6.7 and 4.4.0 through 4.4.18 prior to vendor fixes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service crash in the Wireshark Kerberos protocol dissector.
A Wireshark vulnerability addressed by Debian DSA-6471; the advisory states the set of flaws could cause denial of service or arbitrary-code execution.
A specific vulnerability identified as CVE-2026-76924 affecting Wireshark-related packages on Debian Linux and Red Hat Enterprise Linux systems, with availability impact indicated by the CVSS data.
An out-of-bounds read / heap-buffer-overflow in Wireshark's Kerberos dissector when formatting a preview of short EncryptionKey values learned from plaintext Kerberos credential structures.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.