Quick answers
- Is CVE-2026-105960 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105960 being exploited in the wild.
- How severe is CVE-2026-105960?
- Medium severity, with a CVSS score of 5.5, published 20 October 2026.
- Which products and versions are affected?
- HMS Networks PCAN Windows CAN device drivers <=5.1.2; HMS Networks PEAK-System Device Driver Setup <=5.1.2.1151.
- Is there a fix for CVE-2026-105960?
- Yes: fixed in PEAK-System Device Driver Setup 5.1.4, PCAN Windows CAN device drivers 5.1.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105960 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-105960?
- Check whether you run HMS Networks PCAN Windows CAN device drivers or HMS Networks PEAK-System Device Driver Setup 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.
How to fix
- Fixed in: PEAK-System Device Driver Setup 5.1.4, PCAN Windows CAN device drivers 5.1.4
Technical details
The driver fails to validate caller-supplied output buffer sizes in diagnostic calls and uses unvalidated record counts for variable-length copies without capping to actual output length. CVE-2026-105960 specifically involves insufficient validation of array indices in a receive-record copy operation. All vulnerabilities are triggered locally with low privilege and no user interaction required, resulting in kernel-mode memory corruption and denial of service.
Affected products
- HMS Networks PEAK-System Device Driver Setup <=5.1.2.1151
- HMS Networks PCAN Windows CAN device drivers <=5.1.2
Timeline
- 2026-10-20: disclosed