# CVE-2026-19472: Rockwell Automation ArmorStart® LT Denial Of Service

> An attacker can cause a denial of service on Rockwell ArmorStart LT devices by sending a crafted HTTP PUT request to the embedded web server.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-mh24-4rcj-4gmj

## What is CVE-2026-19472?

CVE-2026-19472 is a high-severity denial of service vulnerability in Rockwell Automation ArmorStart® LT, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial-of-service security issue exists within ArmorStart® LT. The security issue stems from improper handling of a crafted HTTP PUT request sent to the embedded web server. This can result in a loss of web server availability

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-19472?


## How do I fix CVE-2026-19472?

No fix has been published for CVE-2026-19472 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19472 being exploited?

There is no known exploitation of CVE-2026-19472 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19472 and fix it if it is affected.

What it is: CVE-2026-19472 is a high-severity denial of service vulnerability in Rockwell Automation ArmorStart® LT, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19472 in the wild and no public exploit code.

Affected product: Rockwell Automation ArmorStart® LT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19472/ (Markdown: https://insights.sbomify.com/CVE-2026-19472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19472
- OSV: https://osv.dev/vulnerability/CVE-2026-19472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19472/
Summaries are generated and may contain mistakes; the official description above is the record.