Quick answers
- Is CVE-2026-95395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95395 being exploited in the wild.
- How severe is CVE-2026-95395?
- Medium severity, with a CVSS score of 5.5, published 29 September 2026.
- Which products and versions are affected?
- Wireshark Foundation Wireshark 4.6.0 to 4.6.8, 4.4.0 to 4.4.18.
- Is there a fix for CVE-2026-95395?
- A patch was published on 2026-09-29: Fixed in Wireshark 4.6.9 and 4.4.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95395 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-95395?
- Check whether you run Wireshark Foundation Wireshark at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The config_3_frame_fast() function in packet-synphasor.c reads a num_ph (number of phasors) field from malformed packets without upper-bound validation, then allocates up to 17.8 MB per frame using wmem_file_scope(), which is only freed when the capture file closes. An attacker can send multiple crafted IEEE C37.118 CFG3 frames to trigger unbounded memory exhaustion; a single 78-byte UDP packet causes a 17.8 MB allocation, and 1000 frames result in ~17 GB of memory consumption leading to out-of-memory termination.
Affected products
- Wireshark Foundation Wireshark 4.6.0 to 4.6.8, 4.4.0 to 4.4.18
Timeline
- 2026-09-23: disclosed: Wireshark security advisory wnpa-sec-2026-96 published
- 2026-09-29: patched: Fixed in Wireshark 4.6.9 and 4.4.19