CVE-2026-7379 json
Missing Release of Memory after Effective Lifetime in Wireshark
published 2026-04-30 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-26313
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Memory leak in sharkd 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service
Patch / fix
- Wireshark Foundation Wireshark 4.4.15, 4.6.5
- wireshark Debian 13 4.4.15-0+deb13u1
- wireshark Debian 14 4.6.5-1
debian advisories DEBIAN-CVE-2026-7379
- wireshark SLE Module for Desktop Applications 15 SP7, SLE Module for Basesystem 15 SP7 4.6.7-150700.21.11.1
- wireshark SLES 16.0, SLES for SAP applications 16.0 4.4.17-160000.1.1
- wireshark SLES LTSS Extended Security 12 SP5 2.4.16-48.69.1
suse advisories SUSE-SU-2026:3501-1SUSE-SU-2026:23124-1SUSE-SU-2026:23147-1SUSE-SU-2026:2969-1
- wireshark openSUSE Leap 16.0 4.4.17-160000.1.1
- wireshark openSUSE Tumbleweed 4.6.5-1.1
opensuse advisories openSUSE-SU-2026:21534-1openSUSE-SU-2026:10686-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- gitlab.com https://gitlab.com/wireshark/wireshark/-/work_items/21214 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Wireshark Foundation Wireshark
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
-
gitlab.com
/wireshark/wireshark/-/work_items/21214
exploit, vendor-advisory
-
wireshark.org
/security/wnpa-sec-2026-47.html
vendor-advisory
Sources
- CVE List CVE-2026-7379
- NVD CVE-2026-7379
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.