Cyber Resilience

CVE-2026-5403

Memory Safety in Wireshark 4.4.0 – 4.4.15

Public PoCMemory Safety
Published
01 May 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0016 6th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-5403 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Wireshark Wireshark. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-5403 affects the SBC codec dissector in Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. The vulnerability causes a crash due to heap-based buffer overflows (CWE-122 and CWE-787), enabling denial of service and possible code execution. Published on 2026-05-01, it has a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

An attacker with local access can exploit this vulnerability with low complexity and no required privileges, but it necessitates user interaction, such as convincing a Wireshark user to open a malicious packet capture file. Successful exploitation leads to denial of service through application crashes or potential code execution, resulting in high impacts to confidentiality, integrity, and availability on the local system.

For mitigation guidance and patches, refer to the Wireshark security advisory WNPA-SEC-2026-16 at https://www.wireshark.org/security/wnpa-sec-2026-16.html and the related GitLab issue tracker at https://gitlab.com/wireshark/wireshark/-/issues/21103.

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-122CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5405Same product: Wireshark Wireshark
CVE-2023-0667Same product: Wireshark Wireshark
CVE-2026-6530Same product: Wireshark Wireshark
CVE-2026-15169Same product: Wireshark Wireshark
CVE-2026-15165Same product: Wireshark Wireshark
CVE-2026-15170Same product: Wireshark Wireshark
CVE-2026-5653Same product: Wireshark Wireshark
CVE-2026-5402Same product: Wireshark Wireshark
CVE-2026-7378Same product: Wireshark Wireshark
CVE-2026-15164Same product: Wireshark Wireshark

Affected Assets

wireshark
wireshark
4.4.0 — 4.4.15 · 4.6.0 — 4.6.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

SI-10 Information Input Validation good match

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Timely patching removes known heap-overflow instances after they exist.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect heap overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References