CVE-2025-9466
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 · uneditedA security issue exists within ArmorStart® LT that can result in a denial-of-service condition. During execution of the Achilles EtherNet/IP and CIP grammar tests, the device reboots unexpectedly, causing the Link State Monitor to go down for several seconds.
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 confidenceArmorStart LT motor starters contain a denial-of-service vulnerability where execution of Achilles EtherNet/IP and CIP grammar tests triggers an unexpected device reboot, causing the Link State Monitor to go down for several seconds and disrupting industrial operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.002CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the physical device label or consult device inventory/management interface to confirm the model is Rockwell Automation ArmorStart LTAffected if The device is not an ArmorStart LT model, then it is not affected by this CVE
-
Check firmware versionAccess the device management interface or use the appropriate Rockwell automation tool to retrieve the current firmware versionAffected if Firmware version is 2.002 or lower, indicating the device falls within the affected version range
-
Verify if diagnostic test functions are enabledReview device configuration settings to determine whether Achilles EtherNet/IP and CIP grammar test functions are enabled or accessibleAffected if Diagnostic test functions are enabled and accessible, the device is vulnerable to the DoS condition when these tests are executed
-
Review for unexpected reboot eventsCheck device logs, system event logs, or the Link State Monitor status for records of unexpected reboots or Link State Monitor downtimeAffected if Unexpected reboots or Link State Monitor disruptions are present in logs or monitoring data, the device may have been exploited
-
Assess network exposure of management interfacesReview network segmentation and access control lists to determine if device management and diagnostic interfaces are exposed to untrusted networksAffected if Management and diagnostic interfaces are accessible from untrusted networks, the device has higher exposure to potential test execution
A user is affected if they have an ArmorStart LT device with firmware version 2.002 or lower, and the diagnostic test functions are accessible or have been executed, resulting in unexpected reboots.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict network access to the device's management interfaces and disable or isolate diagnostic/test functions if not required for normal operations. Monitor for unexpected reboots and contact Rockwell Automation for firmware remediation.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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