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.
CVE-2026-10573
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 16.8%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (1)
Auto-updated Jul 14, 2026SD1779 | Security Advisory | Rockwell Automation | US
https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1779.htmlVendor Advisories for CVE-2026-10573(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:04 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 02:10 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 14:22 UTCGHSA enrichment
- 2026-07-16 02:33 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:44 UTCGHSA enrichment
- 2026-07-15 02:54 UTCGHSA enrichment
- 2026-07-14 15:06 UTCEG score recompute
- 2026-07-14 15:05 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-770
- CVE-2018-20033EG 9.8CRITICAL
- CVE-2019-11479NVD 7.5EG 9.0EPSS 100%HIGH
- CVE-2019-11478NVD 5.3EG 9.0EPSS 100%MEDIUM
- CVE-2019-10088EG 8.8EPSS 91%HIGH
- CVE-2018-15462EG 8.6HIGH
- CVE-2018-15460EG 8.6HIGH
- CVE-2018-0137EG 8.6HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS 99%MEDIUM
- CVE-2019-10094EG 7.8HIGH
- CVE-2018-16865EG 7.8HIGH
Frequently asked(5)
What is CVE-2026-10573?
When was CVE-2026-10573 disclosed?
Is CVE-2026-10573 actively exploited?
What is the CVSS score of CVE-2026-10573?
How do I remediate CVE-2026-10573?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-10573
Is Your Infrastructure Affected by CVE-2026-10573?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.