CVE-2025-9281
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 Comprehensive step limit storm tests, the device reboots
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 · moderate confidenceArmorStart LT motor starter contains a vulnerability that causes the device to reboot when subjected to network storm tests (Achilles Comprehensive step limit tests). This indicates a lack of proper input validation or rate limiting for network traffic, allowing an attacker to trigger denial-of-service conditions by sending malformed or excessive network packets.
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 ArmorStart LT devices on the networkReview network inventory or use device discovery tools to locate ArmorStart LT motor starters. Check device nameplates, management interfaces, or PLC/hmi project files for ArmorStart LT references.Affected if The environment contains ArmorStart LT motor starters.
-
Determine the installed firmware versionAccess the ArmorStart LT device web interface, Rockwell RSLogix/Studio 5000 environment, or use the device's built-in diagnostic tools to retrieve the firmware version. Compare the version number against 2.002.Affected if The firmware version is 2.002 or lower.
-
Verify network accessibility of the deviceConfirm the ArmorStart LT has an active IP address on the production or adjacent network. Check if the device responds to ping or standard industrial protocols (Ethernet/IP, Modbus TCP).Affected if The device is network-addressable and reachable from any network segment.
-
Assess network segmentation controlsReview firewall rules, VLAN configurations, or network ACLs protecting the ArmorStart LT. Determine if untrusted or external network sources can send traffic directly to the device.Affected if The device is accessible from untrusted network zones or lacks firewall protection.
If the environment contains an ArmorStart LT device with firmware version 2.002 or lower that is network-accessible, the environment is affected by this vulnerability.
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 dataApply vendor-provided firmware updates when available. In the interim, implement network segmentation and firewall rules to restrict untrusted network access to the ArmorStart LT device.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9281 — 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-9281 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