Skip to main content
VulnerabilityPublished

CVE-2025-9464: Rockwell Automation ArmorStart® LT · Uncontrolled Resource Consumption

Affects Rockwell Automation ArmorStart® LTSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 14:05 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 33% 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 20 Jan 2026

  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 AutomationArmorStart® LTAffected
  • =V2.002 and below
Fixed in–

AI-suggested

  1. Network Segmentation: Isolate ArmorStart® LT devices on dedicated network segments with strict access controls to limit exposure to untrusted networks.
  2. Access Control: Restrict access to CIP ports using firewalls or industrial protocol-aware intrusion prevention systems to allow only trusted management stations or controllers.
  3. Traffic Monitoring: Implement continuous monitoring of CIP traffic for anomalous patterns or fuzzing attempts that could indicate exploitation attempts.
  4. Vendor Coordination: Engage with Rockwell Automation for updates and patches; apply security patches promptly once released.
  5. Incident Response Planning: Develop and test response plans for DoS scenarios affecting industrial control devices to minimize downtime.
  6. Device Hardening: Disable unused CIP classes or services on ArmorStart® LT devices to reduce the attack surface.
  7. Network Anomaly Detection: Deploy specialized industrial network anomaly detection tools to identify unusual CIP traffic that could precede exploitation. These measures go beyond generic advice by focusing on network-level controls and proactive monitoring tailored to industrial protocols and environments.

Description

A security issue exists within ArmorStart® LT that can result in a denial-of-service condition. This vulnerability is triggered during fuzzing of multiple CIP classes, which causes the CIP port to become unresponsive.

References

Community reviews

Loading reviews…