Skip to content
IoT

CVE-2025-12011

9.2
Critical
EPSS 0.43%Patch availableJul 15, 2026

Remote DoS causes major non-recoverable fault in 5370/5570 controllers.

common questions

Is CVE-2025-12011 being exploited?

Not confirmed. CVE-2025-12011 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2025-12011?

CVE-2025-12011 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-12011?

Yes. A fix has been recorded for CVE-2025-12011. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-12011 affect?

CVE-2025-12011 affects 5370 controllers, 5570 controllers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-12011?

Isolate affected controllers, block project uploads, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
5370 controllers5570 controllers
impact

Remote attacker can load a malformed project to force controllers into a major non-recoverable fault (MNRF), causing device outage, process disruption and safety risks.

action required

Immediate action required

affected versions
Rockwell Automation CompactLogix® 5370 Compact GuardLogix® 5370 ControlLogix® 5570 GuardLogix® 5570
  • affected35.015 and earlier

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free