dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-10573

HIGH · 8.7 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A denial-of-service security issue exists in 1734 POINT I/O™ module. The security issue stems from improper handling of crafted CIP messages, which can cause the module to enter a faulted state. A restart is required to recover.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A denial-of-service vulnerability exists in the 1734 POINT I/O module due to improper handling of crafted CIP (Common Industrial Protocol) messages. When specially malformed CIP messages are sent to the module, it enters a faulted state and cannot recover until physically or remotely restarted, causing disruption to the industrial process.

MitigationApply vendor firmware updates when available; until then, implement network segmentation to restrict unauthorized CIP message access, and monitor for anomalous traffic patterns that may indicate exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify 1734 POINT I/O modules in your environment
    Review network topology diagrams, PLC hardware configurations, and asset inventories to locate all deployed 1734 POINT I/O modules. Check Rockwell Automation project files and industrial control system documentation for module presence.
    Affected if Any 1734 POINT I/O module is present in the environment and accessible to untrusted network segments.
  2. Determine the firmware version of each 1734 POINT I/O module
    Connect using RSLinx Classic or FactoryTalk Linx, browse to the module in the RSLogix/Studio 5000 device tree, and retrieve the firmware revision from the module properties. Alternatively, access via the web interface if enabled or use ControlFLASH to read the current firmware.
    Affected if The installed firmware version has not been updated to the vendor's fixed revision (check Rockwell Security Advisory for the corrected version number).
  3. Verify network accessibility of the affected module
    Review firewall rules, VLAN configurations, and network segmentation policies to determine if the 1734 POINT I/O module's CIP communication ports (typically UDP/2222, TCP/44818) are accessible from untrusted network segments or the enterprise network.
    Affected if The module accepts CIP messages from network segments that include untrusted or unauthorized devices.
  4. Check for module faulted state indicators
    In RSLogix/Studio 5000, monitor the I/O module health status indicators. Look for modules showing a red fault LED or faulted status in the controller's I/O tree. Review alarm and event logs for unexpected fault entries.
    Affected if The 1734 POINT I/O module is showing an unexplained faulted state that requires physical or remote restart to clear.
  5. Inspect for anomalous CIP traffic patterns
    Analyze network captures or industrial firewall logs for unusual CIP message patterns directed at the 1734 POINT I/O module, particularly malformed or unexpected CIP service requests.
    Affected if Network traffic analysis reveals malformed CIP messages being sent to the module from unauthorized sources.

You are affected if a 1734 POINT I/O module is present in your environment, accessible from untrusted networks, and running firmware older than the vendor's fixed version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available; until then, implement network segmentation to restrict unauthorized CIP message access, and monitor for anomalous traffic patterns that may indicate exploitation attempts.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10573 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data