Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach controller on OT network
-
DeliverySend crafted invalid file data
-
ExploitOverflow unchecked boot-firmware buffer
-
ExecutionController enters major non-recoverable fault
-
ImpactProcess halts until manual recovery
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer copy size validation
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to a controller running boot firmware below version 1.072 and the ability to write file data to it, targeting the CompactLogix 5380/5480, Compact GuardLogix 5380, or ControlLogix/GuardLogix 5580 platforms. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, no special configuration, and no user interaction are required, so any actor able to reach the controller's file-write/management interface can trigger the fault. The primary limiting factor is network exposure: these are OT process controllers normally deployed on segmented industrial networks, so realistic exploitation depends on the attacker first gaining access to that OT segment, and only firmware versions below 1.072 are vulnerable. |
| Impact | The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated attack with no user interaction, which correctly yields a high 9.2 score - but that score is entirely availability-weighted (VA:H, SA:H) with zero confidentiality or integrity impact, so this is a pure DoS, not RCE. There is no EPSS score, no POC, and no CISA KEV entry provided, so exploitation is not confirmed in the wild; the score reflects potential ease of exploitation rather than observed activity. The realistic priority is nonetheless high for operational-technology environments because the impact is a non-recoverable fault requiring physical/manual recovery of a process controller, and many OT networks assume flat, unauthenticated internal reachability. Key caveat: real exposure hinges on network segmentation - if these controllers are properly isolated on an OT network per Rockwell/IEC 62443 guidance, the practical AV:N reachability is greatly reduced; verify segmentation before treating this as internet-exploitable. |
| Exploit ScenarioDerived | An attacker with network reachability to an unpatched Logix controller sends crafted file data over the controller's file-transfer/management interface, and because the boot firmware fails to validate the input size (CWE-120), the malformed data triggers a buffer overflow. Given AV:N/AC:L/PR:N/UI:N, no credentials or user interaction are needed, and the controller is driven into a major non-recoverable fault that stops the controlled physical process until an operator manually recovers the device. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 14, 2026
Denial-of-service in Rockwell Automation CompactLogix/GuardLogix 5380, CompactLogix 5480, and ControlLogix/GuardLogix 5580 controllers running boot firmware below version 1.072 lets a remote unauthenticated attacker write malformed file data that forces the device into a major non-recoverable fault (MNRF), halting the controlled process until manual recovery. The flaw carries a CVSS 4.0 base of 9.2 driven purely by availability impact (no data confidentiality or integrity loss) and requires no authentication or user interaction. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
RemediationAI
Vendor-released patch: boot firmware version 1.072 or later - upgrade all affected CompactLogix 5380/5480, Compact GuardLogix 5380, ControlLogix 5580, and GuardLogix 5580 controllers to boot firmware 1.072+ following the update procedure in Rockwell advisory SD1781 (https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1781.html). Because the target is a live process controller, schedule the update during a maintenance window as reflashing boot firmware typically requires taking the controller offline. Until patching is complete, apply network-level compensating controls: place the controllers on a segmented OT/cell network behind a firewall and deny controller management/file-transfer protocols (e.g. CIP/EtherNet-IP over TCP/UDP 44818 and 2222) from untrusted zones, restrict access to only authorized engineering workstations, and monitor for anomalous file-write traffic - the trade-off is that overly aggressive filtering can disrupt legitimate PLC programming and HMI/SCADA polling, so validate rules against normal traffic before enforcing.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected devices are Rockwell Automation programmable automation controllers (PACs) from the Logix family - CompactLogix 5380, Compact GuardLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 - where the defect lives in the boot/recovery firmware image (per the single CPE covering the '...recovery image' components). The root cause is classified as CWE-120 (Buffer Copy without Checking Size of Input, i.e. a classic buffer overflow) and is tagged 'Buffer Overflow': the firmware copies attacker-supplied file data into a buffer without adequately validating its size or format, so crafted/invalid input overruns the intended bounds and corrupts controller state. Rather than achieving code execution, the overflow drives the controller into an MNRF, a fault state on Logix hardware that requires manual intervention (reflash/recovery) rather than an automatic restart.
Know when Compactlogix 5380 Recovery Image Compact Guardlogix 5380 Recovery Image Compactlogix 5480 Recovery Image Controllogix 5580 Recovery Image Guardlogix 5580 Recovery Image gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
Network-reachable, low-complexity, unauthenticated DoS with no user interaction; scope changes as the controller fault halts the physical process, and only availability is impacted.
Primary rating from Vendor (Rockwell).
CVSS VectorVendor: Rockwell
DescriptionCVE.org
A denial-of-service issue exists in 5380/5480/5580 controllers boot firmware lower than version 1.072. This vulnerability could potentially allow a malicious user to write invalid file data to the controller, causing the device to enter a major non-recoverable fault (MNRF).
Executive ViewAI
Rockwell Automation CompactLogix and ControlLogix industrial controllers (5380, 5480, 5580 models running firmware below version 1.072) are vulnerable to remote denial-of-service attacks that force devices into unrecoverable fault states, halting critical manufacturing processes. An unauthenticated attacker can trigger this vulnerability over the network without user interaction, and no vendor-released patch has been identified at time of analysis. Affected facilities face immediate operational risk until compensating controls are deployed.
Network segmentation isolating affected controllers from external-facing networks; firewall rules restricting remote access with whitelisting of authorized engineering workstations; network intrusion detection/prevention systems monitoring for exploitation attempts; documented manual recovery procedures tested and maintained at each facility; real-time SCADA/process monitoring for unexpected controller faults or state changes; regular vulnerability tracking with Rockwell Automation for patch release notifications.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
EUVD-2025-210463
GHSA-w4jq-g2m7-xj78
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB