CVE-2026-5403 | Heap-based Buffer Overflow in Wireshark

Exp

SBC codec crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service and possible code execution

Published: 2026-05-01 Last update: 2026-05-01 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-5403 is rated Exploit Available (50/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-5403

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-5403

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-01 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-5403

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2026-5403

GitHub Security Advisory for CVE-2026-5403

GHSA-fp9p-ww3j-hpfw · Severity: high — SBC codec crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service and...

OS Trackers for CVE-2026-5403

vendor priority summary link
debian not yet assigned CVE-2026-5403 not yet assigned priority: Debian including 1 source packages (wireshark), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2026-5403
suse medium — https://www.suse.com/security/cve/CVE-2026-5403/
ubuntu medium CVE-2026-5403 medium priority: Ubuntu including 1 source packages (wireshark), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): needs-triage 8, released 1. https://ubuntu.com/security/CVE-2026-5403

Affected software / configurations for CVE-2026-5403

Vendor Product Version Raw CPE
wireshark wireshark >= 4.4.0, < 4.4.15 cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*
wireshark wireshark >= 4.6.0, < 4.6.5 cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*

References for CVE-2026-5403

cvelogic Threat Intelligence