Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-5403: Wireshark SBC Codec Heap Buffer Overflow

Published Apr 30, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.16%5th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wireshark Foundation
IdentifiersCVE-2026-5403CWE-122 · Heap-based Buffer Overflow

CVE-2026-5403 is a heap-based buffer overflow in Wireshark's SBC audio codec processing component. It affects Wireshark 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. Processing malformed SBC audio data can crash Wireshark and may be exploitable for arbitrary code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

An attacker may cause a Wireshark denial of service by triggering an application crash. The heap-based memory corruption may also permit arbitrary code execution, although exploitation was not known to be occurring at disclosure.

Mitigation

If you can’t patch tonight, do this now.

Until patched, do not open untrusted packet-capture files and avoid capturing or decoding untrusted SBC traffic where practical. Limit access to live capture environments, use least privilege for Wireshark execution, and isolate analysis of untrusted captures in a sandboxed or disposable environment.

Remediation

Patch, then assume compromise.

Upgrade Wireshark to version 4.6.5 or later in the 4.6 release branch, or to version 4.4.15 or later in the 4.4 release branch.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Wireshark FoundationWiresharkapplication
FAQ

Frequently asked questions

Is CVE-2026-5403 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5403 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5403?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-5403.
Is there a patch for CVE-2026-5403?
Upgrade Wireshark to version 4.6.5 or later in the 4.6 release branch, or to version 4.4.15 or later in the 4.4 release branch.
What products are affected by CVE-2026-5403?
Wireshark Foundation Wireshark.
How severe is CVE-2026-5403?
CVE-2026-5403 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.16% (5th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.