Service interruption via unreleased capture state
Published Apr 30, 2026 · Updated Apr 30, 2026
Memory leak in Wireshark sharkd 4.4.0 through 4.4.14 and 4.6.0 through 4.6.4 allows local users to exhaust memory via repeated loads. The cf_open function overwrites the existing capture handle, filename, and frame provider without freeing their prior allocations. Reachability requires access to sharkd's standard input or JSON-RPC socket; repeated load requests cause unbounded memory growth and service interruption.
Summary
What happened
Memory leak in Wireshark sharkd 4.4.0 through 4.4.14 and 4.6.0 through 4.6.4 allows local users to exhaust memory via repeated loads. The cf_open function overwrites the existing capture handle, filename, and frame provider without freeing their prior allocations. Reachability requires access to sharkd's standard input or JSON-RPC socket; repeated load requests cause unbounded memory growth and service interruption.
The record
- CVE
- CVE-2026-7379
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-401, T1499.003
- 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.
Weakness, pattern, technique
Public exploit references
- sharkd repeated-load proof of conceptproof 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