1734 POINT I/O CVE-2026-10573

Exploitation requires network reachability to a 1734 POINT I/O module's EtherNet/IP/CIP interface and the ability to send a crafted CIP message; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, privileges, or user interaction are needed against a reachable module. The primary limiting factor is network exposure: in correctly segmented OT architectures the module is not routable from IT or untrusted networks, so an attacker must first gain a foothold on the control network. Impact is limited to availability - the device faults and requires a manual restart to recover - with no confidentiality or integrity effect (VC:N/VI:N/VA:H).

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H) is internally consistent with the description: a network-reachable, low-complexity, unauthenticated attack with pure availability impact and no confidentiality or integrity loss. In IT terms this is a moderate score, but in an OT/ICS context a forced fault requiring manual restart of distributed I/O can halt a physical process, making real-world operational impact potentially severe. No EPSS score, KEV listing, or POC was provided, so exploitation likelihood cannot be quantified from the input; the practical exposure hinges almost entirely on whether the module is reachable from untrusted networks - in properly segmented OT environments the network vector is substantially constrained. No conflicting signals are present, though the absence of EPSS/POC data means exploitation probability is genuinely unknown rather than low.

An attacker with access to the OT network - for example after pivoting from a compromised engineering workstation or through an inadequately segmented cell/area zone - sends a crafted CIP message to a 1734 POINT I/O module over EtherNet/IP. Because no authentication or user interaction is required (AV:N/PR:N/UI:N) and complexity is low, the malformed message drives the module into a faulted state, stopping I/O and forcing a manual restart to recover. No public exploit code has been identified, but the low attack complexity makes reliable disruption plausible once the device is reachable.