dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-11698

CRITICAL · 9.2 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial-of-service vulnerability exists in 5380/5480/5580 controller boot firmware versions prior to 1.072. An authenticated malicious user can write invalid file data to the controller, triggering a Major Non-Recoverable Fault (MNRF) that renders the device unusable. The CVSS 9.2 score indicates trivial exploitability with complete loss of device availability.

MitigationUpgrade controller boot firmware to version 1.072 or higher to remediate this vulnerability. Since MNRF faults are non-recoverable, ensure firmware updates are performed with validated images and maintain rollback capabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify controller model
    Access the device management interface (CLI, web UI, or console) and retrieve the hardware model number. Look for 5380, 5480, or 5580 in the model identification output.
    Affected if Model is not 5380, 5480, or 5580 (different models are not affected by this specific CVE)
  2. Retrieve boot firmware version
    Run the command to display firmware versions. Common commands include 'show version', 'show firmware', or 'show boot-info' depending on the controller interface. Locate the boot firmware or primary firmware version string.
    Affected if Cannot retrieve a version number or the device is not a controller from this product line
  3. Compare version against affected range
    Compare the installed boot firmware version to the affected range (prior to 1.072). Note the exact version number displayed (for example, 1.060, 1.070, 1.071 would be affected; 1.072 and later are not).
    Affected if Installed boot firmware version is below 1.072 (for example, 1.060, 1.065, 1.071)
  4. Verify authentication status
    Confirm whether user authentication is enabled on the device management interface. Check for local user accounts, RADIUS, TACACS+, or other authentication methods. Use 'show users' or 'show authentication' commands.
    Affected if No authentication is required to access device management (authentication is required for the exploit to work)
  5. Check firmware write access controls
    Review user privilege levels and access controls. Identify which accounts have permission to write or upload firmware. Look for privilege levels that permit firmware operations.
    Affected if Users with write access to firmware exist and authentication alone is sufficient (the exploit requires an authenticated user who can write to firmware)

If the controller is a 5380, 5480, or 5580 model with boot firmware version prior to 1.072 AND the device allows authenticated users to write firmware, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade controller boot firmware to version 1.072 or higher to remediate this vulnerability. Since MNRF faults are non-recoverable, ensure firmware updates are performed with validated images and maintain rollback capabilities.

Recommended fix High confidence

Boot firmware version 1.072 for 5380/5480/5580 controllers

  1. Identify the specific controller model (5380, 5480, or 5580) in the environment
  2. Check the current boot firmware version on the affected controller(s)
  3. Navigate to Rockwell Automation's technical support website and locate the firmware download section
  4. Download boot firmware version 1.072 for the specific controller model
  5. Follow Rockwell Automation's documented firmware update procedure to upgrade the controller's boot firmware to version 1.072
  6. After upgrade, verify the firmware version has been correctly applied and the controller is operating normally
  7. Test that the controller can handle file operations without entering a major non-recoverable fault (MNRF)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11698 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data