# CVE-2025-9124: Rockwell Automation Compact GuardLogix® 5370 Denial-Of-Service Vulnerability

> Attackers can cause a major non-recoverable fault in Rockwell Compact GuardLogix 5370 controllers by sending crafted CIP messages.

- **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:** 14 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-98v9-3hq2-88q8

## What is CVE-2025-9124?

CVE-2025-9124 is a high-severity denial of service vulnerability in Rockwell Automation Compact GuardLogix® 5370, published on 14 Oct 2025. 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 in the affected product. The security issue stems from a fault occurring when a crafted CIP unconnected explicit message is sent. This can result in a major non-recoverable fault.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2025-9124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9124 is a high-severity denial of service vulnerability in Rockwell Automation Compact GuardLogix® 5370, published on 14 Oct 2025. 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-2025-9124 in the wild and no public exploit code.

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

## Sources

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

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