CVE-2025-9280: Rockwell Automation ArmorStart® LT · Uncontrolled Resource Consumption
Affects Rockwell Automation ArmorStart® LTSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 06:26 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 2026
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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rockwell AutomationArmorStart® LT | Affected
| Fixed in– |
AI-suggested
1. Implement network segmentation to isolate ArmorStart® LT devices from general IT networks and limit exposure to untrusted networks. 2. Monitor device behavior and network traffic for signs of abnormal resource consumption or unresponsiveness, using industrial control system (ICS) monitoring tools. 3. Apply strict input validation and filtering at network boundaries to block malformed or unexpected packets targeting ArmorStart® LT devices. 4. Engage with Rockwell Automation for updates or patches addressing this vulnerability and plan for timely deployment once available. 5. Develop and test incident response procedures to quickly reboot or restore affected devices to minimize downtime. 6. Conduct regular vulnerability assessments and penetration testing focused on industrial control systems to identify similar weaknesses. 7. Maintain an inventory of all ArmorStart® LT devices and their firmware versions to prioritize remediation efforts. 8. Educate operational technology (OT) personnel about this vulnerability and encourage vigilance for signs of exploitation.
Description
A security issue exists within ArmorStart® LT that can result in a denial-of-service condition. Fuzzing performed using Defensics causes the device to become unresponsive, requiring a reboot.