# CVE-2025-11743: Rockwell Automation CompactLogix® 5370 Denial of Service Vulnerability

> Attackers can cause a major nonrecoverable fault requiring a restart by sending a malformed CIP forward open message to CompactLogix 5370 controllers.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-f82p-7gv2-xxj9

## What is CVE-2025-11743?

CVE-2025-11743 is a high-severity denial of service vulnerability in Rockwell Automation CompactLogix® 5370, published on 20 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A denial-of-service security issue in the affected product. The security issue occurs when a malformed CIP forward open message is sent. This could result in a major nonrecoverable fault a restart is required to recover.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2025-11743?


## How do I fix CVE-2025-11743?

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

## Is CVE-2025-11743 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11743 and fix it if it is affected.

What it is: CVE-2025-11743 is a high-severity denial of service vulnerability in Rockwell Automation CompactLogix® 5370, published on 20 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11743 in the wild and no public exploit code.

Affected product: Rockwell Automation CompactLogix® 5370. 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-2025-11743/ (Markdown: https://insights.sbomify.com/CVE-2025-11743/index.md)
```

## Sources

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

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