Loading vulnerability…
CVE-2026-5403 is a heap-based buffer overflow in Wireshark's SBC audio codec processing. The flaw affects Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14 and is tracked in Wireshark issue 21103 and advisory wnpa-sec-2026-16. When Wireshark decodes malformed SBC audio data from live network traffic or from a crafted packet capture, the vulnerable codec logic can write or read beyond the bounds of a heap buffer, causing a crash and creating a potential path to arbitrary code execution.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced as part of the Wireshark 4.6.8 advisory/plugin CVE list, but not described individually in the content.
A vulnerability in Wireshark's SBC codec that may allow code execution via crafted audio payloads.
A Wireshark SBC codec processor vulnerability that can cause a crash with possible code execution.
A vulnerability in Wireshark's SBC audio codec that can cause a crash and may allow arbitrary code execution via a malformed packet or malformed packet trace file.
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.