Quick answers
- Is CVE-2026-103672 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103672 being exploited in the wild.
- How severe is CVE-2026-103672?
- High severity, with a CVSS score of 7.1, 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-103672?
- Yes: fixed in HMS Networks 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-103672 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-103672?
- 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: HMS Networks PEAK-System Device Driver Setup 5.1.4; PCAN Windows CAN device drivers 5.1.4
Technical details
The PCAN parser uses an attacker-controlled DLC value to index a length table without enforcing the valid range (DLC ≤ 0x0f), then performs an unchecked copy of attacker payload from a fixed offset into a fixed-size stack buffer. This is a classic out-of-bounds write vulnerability reachable via the file-device write path with low privilege, leading to kernel crash.
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