CVE-2026-95390: Wireshark PEAK CAN TRC file parser crash

CVE-2026-95390 · Severity: medium · CVSS 5.5 · Published 2026-09-29

Wireshark, a widely-used network analysis tool, contains a bug in its PEAK CAN TRC file parser that crashes the application when processing malformed capture files. An attacker could craft a malicious 44-byte or 46-byte PEAK TRC file that, when opened in Wireshark, causes an immediate crash, resulting in denial of service for network troubleshooting operations.

Technologies: Wireshark Foundation Wireshark. Vendors: Wireshark Foundation.

Quick answers

Is CVE-2026-95390 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-95390 being exploited in the wild.
How severe is CVE-2026-95390?
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-95390?
A patch was published on 2026-09-29: Fixed in Wireshark 4.6.9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-95390 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-95390?
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 vulnerability is a NULL pointer dereference in the PEAK TRC v1 ERROR-frame parser (wiretap/peak-trc.c). The parser splits the data column and accesses bytes[0] or bytes[1] without first validating the token count, allowing incomplete ERROR-frame columns to trigger a crash during automatic format detection. The attack requires only local file access—opening a crafted TRC file causes an immediate SIGSEGV with no user interaction beyond opening the file.

Affected products

  • Wireshark Foundation Wireshark 4.6.0 to 4.6.8

Timeline

  • 2026-09-23: disclosed
  • 2026-09-29: patched: Fixed in Wireshark 4.6.9

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.