Skip to main content
VulnerabilityPublished

CVE-2025-9166: Rockwell Automation ControlLogix® 5580 · NULL Pointer Dereference

Affects Rockwell Automation ControlLogix® 5580Source CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 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 ControlLogix® 5580Affected
  • =35.013
Fixed in–

AI-suggested

1. Immediate network segmentation: Isolate ControlLogix® 5580 controllers from general IT networks and restrict access to trusted management stations only. 2. Implement strict firewall rules and access control lists (ACLs) to limit inbound traffic to the controllers, allowing only necessary protocols and IP addresses. 3. Monitor network traffic for unusual message forwarding patterns that could indicate exploitation attempts. 4. Apply compensating controls such as intrusion detection/prevention systems (IDS/IPS) tuned for ICS protocols to detect anomalies. 5. Coordinate with Rockwell Automation for timely patch releases and apply updates as soon as they become available. 6. Conduct thorough inventory and asset management to identify all affected controllers running version 35.013. 7. Develop and test incident response plans specific to ICS DoS events to minimize downtime. 8. Where possible, implement redundant controllers or failover mechanisms to maintain operational continuity during faults. 9. Restrict physical access to controllers to prevent local exploitation or tampering. 10. Engage with ICS cybersecurity specialists to perform vulnerability assessments and penetration testing focused on this vulnerability.

Description

A denial-of-service security issue exists in the affected product and version. The security issue stems from the controller repeatedly attempting to forward messages. The issue could result in a major nonrecoverable fault on the controller.

References

Community reviews

Loading reviews…