Cyber Resilience

CVE-2026-5657

Memory Safety in Wireshark 4.4.0 – 4.4.14

Public PoCMemory Safety
Published
30 April 2026
Modified
01 May 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0021 11th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2026-5657 is a medium-severity Double Free (CWE-415) vulnerability in Wireshark Wireshark. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 11th 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 SA-8 (Security and Privacy Engineering Principles) — 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-5657 is a vulnerability in the iLBC codec implementation within Wireshark versions 4.6.0 through 4.6.4 and 4.4.0 through 4.4.14. The flaw, classified under CWE-415 (Double Free), triggers a crash that results in a denial-of-service condition. It carries a CVSS v3.1 base score of 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) and was published on 2026-04-30.

An attacker with local access can exploit this vulnerability with low complexity and no required privileges, though it demands user interaction, such as convincing a user to open a malicious packet capture file containing crafted iLBC codec data. Successful exploitation crashes the Wireshark application, causing a high-impact denial of service on availability without compromising confidentiality or integrity.

Wireshark's security advisory WNPA-SEC-2026-20 documents the issue, with related discussions and fixes tracked in GitLab issues #21113 and work item 21113. Mitigation involves updating to patched versions of Wireshark outside the affected ranges.

EU & UK References

Vulnerability Data

iLBC codec crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
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.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-7378Same product: Wireshark Wireshark
CVE-2023-3648Same product: Wireshark Wireshark
CVE-2026-15165Same product: Wireshark Wireshark
CVE-2026-15167Same product: Wireshark Wireshark
CVE-2024-24478Same product: Wireshark Wireshark
CVE-2026-6530Same product: Wireshark Wireshark
CVE-2026-15169Same product: Wireshark Wireshark
CVE-2026-6868Same product: Wireshark Wireshark
CVE-2026-5654Same product: Wireshark Wireshark
CVE-2026-6538Same product: Wireshark Wireshark

Affected Assets

wireshark
wireshark
4.4.0 — 4.4.14 · 4.6.0 — 4.6.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation explicitly includes dynamic analysis and fuzzing that locate double-free defects before release.

Security engineering principles can require memory-safe allocation patterns or language features that structurally eliminate double-free opportunities.

Flaw remediation processes require identification and correction of memory-management defects such as double free once discovered.

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 SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.

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.

finds

Security testing in development can detect double-free conditions before release.

prevents

Secure development life cycle includes memory-safety practices that can prevent double-free bugs.

prevents

Application security requirements can mandate memory-safety rules that reduce double-free risk.

prevents

Secure system architecture and engineering principles can prescribe safe memory-management patterns.

prevents

Secure coding standards directly address proper use of free() and similar functions.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248590 OL 8 must clear the page allocator to prevent use-after-free attacks. prevents CWE-415

References