CVE Intelligence
High

CVE-2026-103672 — HMS Networks PEAK-System PCAN Windows drivers Improper Validation of Array Index

The PEAK-System PCAN parser indexes a length table using attacker-controlled DLC without enforcing DLC <= 0x0f, then copies attacker payload from record+0x1c into a fixed-size stack destination.

Published Oct 20, 2026 · Updated Oct 20, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: icscert

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.13%
ahead of 2% of scored CVEs · Oct 21, 2026
Affects
HMS Networks
PCAN Windows CAN device drivers and 1 more
CVSS base
7.1
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (HMS Networks PCAN Windows CAN device drivers, HMS Networks PEAK-System Device Driver Setup).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
HMS Networks PCAN Windows CAN device drivers ≤ 5.1.2 Vulnerable CVE Program (cve.org) e CISA ADP
HMS Networks PEAK-System Device Driver Setup ≤ 5.1.2.1151 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 4.0 Medium — — ics-cert@hq.dhs.gov via NIST National Vulnerability Database
6.9 CVSS 4.0 Medium — — icscert via CVE Program (cve.org) e CISA ADP
7.1 CVSS 3.1 High 1.8 5.2 ics-cert@hq.dhs.gov via NIST National Vulnerability Database
7.1 CVSS 3.1 High — — icscert via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (score shown at the top: ics-cert@hq.dhs.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-129

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · hms networks/peak-system device driver setup, hms networks/pcan windows can device drivers
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 20, 2026
  • CVSS changed · 7.1
    Oct 20, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 20, 2026 · Alertas do Telegram
  • CVE published
    Oct 20, 2026 · icscert

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 20, 2026 – Oct 20, 2026
  • 1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

4 on the record

Elsewhere on this site

HMS Networks
every CVE for this vendor
CWE-129
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-110322 HMS Networks PEAK-System PCAN Windows drivers Untrusted Pointer Dereference 1d
  • CVE-2026-105960 HMS Networks PEAK-System PCAN Windows drivers Improper Handling of Length Parameter Inconsistency 1d
  • CVE-2026-109576 HMS Networks PEAK-System PCAN Windows drivers Out-of-bounds Write 1d
  • CVE-2026-101103 HMS Networks PEAK-System PCAN Windows drivers Classic Buffer Overflow 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-103672 is "HMS Networks PEAK-System PCAN Windows drivers Improper Validation of Array Index", rated High. It affects PCAN Windows CAN device drivers (HMS Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.