CVE-2026-130467 in Wireshark
Summary
by MITRE • 11/20/2026
PEAK CAN TRC file parser crash when built with older versions of GLib in 4.6.0 to 4.6.9 allows denial of service
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified involves a critical flaw within the PEAK-System Technology Control and Recording (TRC) file parser, specifically affecting software versions ranging from 4.6.0 through 4.6.9 when compiled with older iterations of the GLib library framework. This issue manifests as an application crash triggered by malformed or specially crafted TRC input files, leading to a denial of service condition for users relying on this tool for automotive network analysis and debugging tasks. The root cause lies in improper boundary checking during memory allocation operations handled by the legacy GLib components integrated into these specific software releases. When the parser processes certain data structures within the TRC file format that exceed expected limits or contain unexpected metadata, it fails to validate input lengths prior to attempting buffer access, resulting in a segmentation fault or unhandled exception that terminates the process abruptly.
From a technical perspective, this vulnerability is classified under CWE-125, which denotes Out-of-Bounds Read, and potentially CWE-400 for Uncontrolled Resource Consumption if the malformed data triggers excessive memory usage before the crash occurs. The exploitation vector typically requires an attacker to provide a maliciously constructed TRC file that contains specific byte sequences or header anomalies designed to trigger the faulty code path within the parser logic. Since the vulnerability is tied to older versions of GLib, it highlights the risks associated with maintaining legacy dependencies in security-critical applications without regular updates to underlying system libraries. The lack of robust input validation means that any user opening a compromised file will experience an immediate loss of service, disrupting workflows related to CAN bus analysis and vehicle diagnostics.
The operational impact of this denial of service vulnerability is significant for professionals who depend on continuous availability of diagnostic tools in time-sensitive environments such as automotive manufacturing or incident response scenarios. An attacker could distribute malicious TRC files via email attachments, shared network drives, or compromised repositories to induce crashes in target systems. While the primary effect is a crash rather than arbitrary code execution, repeated exploitation can lead to resource exhaustion if the application attempts recovery mechanisms that are also flawed due to the underlying GLib limitations. Furthermore, in automated analysis pipelines where TRC files are processed programmatically, this vulnerability could halt entire data processing workflows, causing downstream failures in reporting or logging systems that depend on successful parsing of these network trace logs.
Mitigation strategies should prioritize immediate upgrading to a version of PEAK-System software beyond 4.6.9, which likely includes patches for the parser logic and updated dependencies. If upgrading is not immediately feasible, users must exercise strict caution when handling TRC files from untrusted sources, employing sandboxing techniques or virtual machines to isolate potential crashes from production environments. Additionally, organizations should review their dependency management policies to ensure that GLib versions are kept current across all development builds, as older library versions often lack modern security hardening features and bug fixes related to memory safety. Implementing input validation layers at the application level can also serve as a compensating control by filtering out anomalous data structures before they reach the vulnerable parser components.