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

Source: https://junglewise.ai/threats/cve-2026-95390-peak-can-trc-file-parser-crash-in-4-6-0-to-4-6-8-allows-denial-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

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](https://junglewise.ai/threats/technologies/wireshark-foundation-wireshark). Vendors: [Wireshark Foundation](https://junglewise.ai/threats/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

- [https://gitlab.com/wireshark/wireshark/-/work_items/21503](https://gitlab.com/wireshark/wireshark/-/work_items/21503)
- [https://www.wireshark.org/security/wnpa-sec-2026-95.html](https://www.wireshark.org/security/wnpa-sec-2026-95.html)

## Related threats

- [Wireshark X11 dissector out-of-bounds heap read](https://junglewise.ai/threats/cve-2026-96423-x11-protocol-dissector-crash-in-4-6-0-to-4-6-8-and-4-4-0-to-4-4)
- [Wireshark Frame protocol metadissector crash](https://junglewise.ai/threats/cve-2026-96422-frame-protocol-metadissector-crash-in-4-6-0-to-4-6-8-and-4-4-0-to)
- [Wireshark Toshiba file parser crash](https://junglewise.ai/threats/cve-2026-96420-toshiba-file-parser-crash-in-4-6-0-to-4-6-8-and-4-4-0-to-4-4-18)
- [Wireshark profile import path traversal code execution](https://junglewise.ai/threats/cve-2026-96419-profile-import-crash-in-4-6-0-to-4-6-8-and-4-4-0-to-4-4-18-allows)
- [Wireshark TIFF dissector infinite loop](https://junglewise.ai/threats/cve-2026-96418-tiff-protocol-dissector-infinite-loop-in-4-6-0-to-4-6-8-and-4-4-0)