# CVE-2025-3128: Mitsubishi Electric Europe smartRTU OS Command Injection

> Remote attackers can execute arbitrary OS commands on Mitsubishi smartRTU devices, leading to data compromise or denial of service.

- **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:** 21 Aug 2025
- **Updated:** 22 Aug 2025
- **Also known as:** GHSA-6c7p-gpwf-3j7p

## What is CVE-2025-3128?

CVE-2025-3128 is a critical command injection vulnerability in Mitsubishi Electric Europe smartRTU, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote unauthenticated attacker who has bypassed authentication could 
execute arbitrary OS commands to disclose, tamper with, destroy or 
delete information in Mitsubishi Electric smartRTU, or cause a denial-of
 service condition on the product.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-3128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3128 is a critical command injection vulnerability in Mitsubishi Electric Europe smartRTU, published on 21 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-3128 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Europe smartRTU. 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-3128/ (Markdown: https://insights.sbomify.com/CVE-2025-3128/index.md)
```

## Sources

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

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