Crash via unchecked PEAK TRC error-frame tokens
Published Sep 29, 2026 · Updated Sep 29, 2026
A malformed PEAK CAN TRC trace in Wireshark 4.6.0 through 4.6.8 allows attackers to crash the reader when a user opens the file. The wiretap/peak-trc.c v1 ERROR-frame parser passes missing data tokens to g_ascii_strtoull() without checking the split-token count, dereferencing NULL. An attacker must induce someone to open the crafted trace; the demonstrated consequence is a reader crash, not code execution.
Summary
What happened
A malformed PEAK CAN TRC trace in Wireshark 4.6.0 through 4.6.8 allows attackers to crash the reader when a user opens the file. The wiretap/peak-trc.c v1 ERROR-frame parser passes missing data tokens to g_ascii_strtoull() without checking the split-token count, dereferencing NULL. An attacker must induce someone to open the crafted trace; the demonstrated consequence is a reader crash, not code execution.
The record
- CVE
- CVE-2026-95390
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-476
- 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
- Minimized malformed PEAK TRC traceproof of concept · demonstrated
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