Quick answers
- Is CVE-2026-95392 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95392 being exploited in the wild.
- How severe is CVE-2026-95392?
- 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, and 4.7.0-4.7.3rc0 development snapshots.
- Is there a fix for CVE-2026-95392?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-95392 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-95392?
- 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
A 32-bit unsigned integer overflow in the GSM/ASCII 7-bit decoder length calculation causes a mismatch between the bounds-checked byte span and the actual decoder loop iteration count. The MBIM dissector reads SizeInBytes and SizeInCharacters independently without validation; crafted values cause the length calculation to wrap, passing the bounds check with a small or zero-byte window while the decoder iterates over the attacker-controlled character count, resulting in heap buffer over-read. Attack vector is via untrusted capture files parsed through tshark/Wireshark's file-reading interface.
Affected products
- Wireshark Foundation Wireshark 4.6.0 to 4.6.8, 4.4.0 to 4.4.18, and 4.7.0-4.7.3rc0 development snapshots
Timeline
- 2026-09-29: disclosed