# CVE-2025-7353: Rockwell Automation ControlLogix® Ethernet Remote Code Execution Vulnerability

> Remote attackers can execute code and modify memory on Rockwell ControlLogix Ethernet modules via the web-based debugger agent.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-cfc3-wwcp-8574

## What is CVE-2025-7353?

CVE-2025-7353 is a critical code injection vulnerability in Rockwell Automation 1756-EN2F/C, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security issue exists due to the web-based debugger agent enabled on Rockwell Automation ControlLogix® Ethernet Modules. If a specific IP address is used to connect to the WDB agent, it can allow remote attackers to perform memory dumps, modify memory, and control execution flow.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2025-7353 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7353 is a critical code injection vulnerability in Rockwell Automation 1756-EN2F/C, published on 14 Aug 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-7353 in the wild and no public exploit code.

Affected product: Rockwell Automation 1756-EN2F/C. 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-7353/ (Markdown: https://insights.sbomify.com/CVE-2025-7353/index.md)
```

## Sources

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

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