Application crash via caller-owned codec context double-free
Published Apr 30, 2026 · Updated Apr 30, 2026
Double free in Wireshark 4.4.0 through 4.4.14 and 4.6.0 through 4.6.4 allows attackers to crash the application via iLBC RTP data. codec_iLBC_release() frees the caller-owned codec context, and the caller later frees the same pointer again when releasing the decoder. The demonstrated path requires opening a malformed capture, playing its iLBC RTP stream, and closing Wireshark, which terminates the process without reported data disclosure or modification.
Summary
What happened
Double free in Wireshark 4.4.0 through 4.4.14 and 4.6.0 through 4.6.4 allows attackers to crash the application via iLBC RTP data. codec_iLBC_release() frees the caller-owned codec context, and the caller later frees the same pointer again when releasing the decoder. The demonstrated path requires opening a malformed capture, playing its iLBC RTP stream, and closing Wireshark, which terminates the process without reported data disclosure or modification.
The record
- CVE
- CVE-2026-5657
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 2026CVE publishedPublication date reported by the CVE source.
- Apr 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.4.0 <4.4.15
- Affected versionversion=4.6.0 <4.6.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- iLBC double-free sample captureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo