Analysis hang via undersized TTL block size
Published Sep 29, 2026 · Updated Sep 29, 2026
Denial of service in Wireshark 4.6.0 through 4.6.8 allows attackers to hang packet-trace analysis with a malformed TTL file. The TTL reader accepts a file-controlled two-byte block size, then repeatedly seeks beyond end-of-file after classifying an entry as corrupt instead of stopping. A user must open the crafted trace; the resulting retry loop consumes a CPU core and floods warnings, without reported data disclosure or code execution.
Summary
What happened
Denial of service in Wireshark 4.6.0 through 4.6.8 allows attackers to hang packet-trace analysis with a malformed TTL file. The TTL reader accepts a file-controlled two-byte block size, then repeatedly seeks beyond end-of-file after classifying an entry as corrupt instead of stopping. A user must open the crafted trace; the resulting retry loop consumes a CPU core and floods warnings, without reported data disclosure or code execution.
The record
- CVE
- CVE-2026-95386
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-835, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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.6.0 <4.6.9
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started