Skip to main content
VulnerabilityPublished

CVE-2025-9041: Rockwell Automation FLEX 5000 I/O · Improper Validation of Specified Type of Input

Affects Rockwell Automation FLEX 5000 I/OSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Rockwell Automation FLEX 5000 I/OAffected
  • <=2.011
Fixed in–

AI-suggested

Organizations should immediately identify and inventory all FLEX 5000 I/O modules running version 2.011 or below, prioritizing those with the 5094-IF8 device. Until a patch is available, implement network segmentation and strict access controls to limit exposure of these devices to untrusted networks. Employ industrial firewall rules to block unauthorized CIP Class 32 requests, especially those targeting inhibited modules. Monitor network traffic for anomalous CIP messages and implement intrusion detection systems tailored for industrial protocols. Establish procedures for rapid manual power cycling to recover modules if faults occur. Engage with Rockwell Automation for updates on patches or firmware upgrades and plan for timely deployment once available. Additionally, review and harden operational procedures to minimize the use of module inhibition unless necessary, reducing the attack surface. Conduct staff training to recognize and respond to module fault states promptly.

Description

A security issue exists due to improper handling of CIP Class 32’s request when a module is inhibited on the 5094-IF8 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.

References

Community reviews

Loading reviews…