Quick answers
- Is CVE-2026-95386 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95386 being exploited in the wild.
- How severe is CVE-2026-95386?
- 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.
- Is there a fix for CVE-2026-95386?
- A patch was published on 2026-09-23: Fix available in Wireshark 4.6.9 or later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95386 attacked?
- It is attacked with local access, in a web application.
- Am I affected by CVE-2026-95386?
- 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 TTL parser in wiretap/ttl.c accepts a file-controlled block_size value (including undersized values like 2 bytes) and repeatedly seeks to computed block boundaries without validating EOF or progress bounds. When a block is corrupted, the parser seeks to the next computed block position and retries, but if the seek goes beyond EOF, it succeeds and retries remain classified as corrupted, creating an endless two-byte advance loop. The vulnerability requires only opening a crafted TTL file (local file access) and affects Wireshark versions 4.6.0 through 4.6.8.
Affected products
- Wireshark Foundation Wireshark 4.6.0 to 4.6.8
Timeline
- 2026-09-23: disclosed
- 2026-09-29: advisory
- 2026-09-23: patched: Fix available in Wireshark 4.6.9 or later