# CVE-2025-1038: Command injection in TropOS 4th Gen

> Authenticated high-privilege users can inject commands to execute SUID applications and gain root access on TropOS devices.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-28jm-jxrw-gvxg

## What is CVE-2025-1038?

CVE-2025-1038 is a high-severity command injection vulnerability in Hitachi Energy TropOS 4th Gen, published on 28 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The “Diagnostics Tools” page of the web-based configuration utility does not properly validate user-controlled input, allowing an authenticated user with high privileges to inject commands into the command shell of the TropOS 4th Gen device. The injected commands can be exploited to execute several set-uid (SUID) applications to ultimately gain root access to the TropOS device.

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

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


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

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

## Is CVE-2025-1038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1038 is a high-severity command injection vulnerability in Hitachi Energy TropOS 4th Gen, published on 28 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1038 in the wild and no public exploit code.

Affected product: Hitachi Energy TropOS 4th Gen. 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-1038/ (Markdown: https://insights.sbomify.com/CVE-2025-1038/index.md)
```

## Sources

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

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