Skip to main content
VulnerabilityPublished

CVE-2025-9278: 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, 10:12 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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. Immediately restrict network access to ArmorStart® LT devices by implementing strict firewall rules and network segmentation to isolate these devices from untrusted or general-purpose networks.
  2. Disable or limit exposure of the web application interface to only trusted management networks or VPNs.
  3. Monitor network traffic for scanning activity, especially from tools like Burp Suite or unusual ICMP traffic patterns, and block suspicious sources.
  4. Implement rate limiting or intrusion prevention systems (IPS) that can detect and mitigate resource exhaustion attempts.
  5. Coordinate with Rockwell Automation for updates on patches or firmware upgrades addressing this vulnerability and plan timely deployment once available.
  6. Conduct internal audits to inventory all ArmorStart® LT devices and verify their firmware versions to identify vulnerable units.
  7. Develop incident response plans that include procedures for manual control or fallback operations in case of device unavailability.
  8. Educate operational technology (OT) personnel about the risks of exposing ICS devices to scanning and unauthorized access.
  9. Consider deploying network anomaly detection solutions tailored for ICS environments to detect early signs of exploitation attempts.

Description

A security issue exists within ArmorStart® LT that can result in a denial-of-service condition. After running a Burp Suite active scan, the device loses ICMP connectivity, causing the web application to become inaccessible.

References

Community reviews

Loading reviews…