CVE-2025-9042: Rockwell Automation FLEX 5000 I/O · Improper Validation of Specified Type of Input
Affects Rockwell Automation FLEX 5000 I/OSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rockwell Automation FLEX 5000 I/O | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should include network segmentation and strict access controls to limit exposure of FLEX 5000 I/O modules to untrusted networks. 2. Implement firewall rules to block unauthorized CIP Class 32 traffic from reaching the 5094-IY8 devices. 3. Monitor network traffic for unusual CIP requests that could trigger the fault state. 4. Establish physical access controls and rapid response procedures to power cycle affected modules if a fault occurs. 5. Coordinate with Rockwell Automation for timely release and deployment of patches or firmware updates addressing this vulnerability. 6. Conduct thorough inventory and risk assessments of all FLEX 5000 I/O modules in use to prioritize remediation efforts. 7. Consider deploying intrusion detection systems specialized for industrial protocols to detect exploitation attempts. 8. Train OT personnel on recognizing symptoms of this fault and on incident response protocols to minimize downtime.
Description
A security issue exists due to improper handling of CIP Class 32’s request when a module is inhibited on the 5094-IY8 device. It causes the module to enter a fault state with the Module LED flashing red. Upon un-inhibiting, the module returns a connection fault (Code 16#0010), and the module cannot recover without a power cycle.