# CVE-2025-7740: Use of default credentials vulnerability in Hitachi Energy SuprOS product

> An authenticated local attacker can use default admin credentials to gain elevated privileges in Hitachi Energy SuprOS.

- **Severity:** High 8.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 28 Jan 2026
- **Also known as:** GHSA-cgx8-hg5r-9pwr

## What is CVE-2025-7740?

CVE-2025-7740 is a high-severity vulnerability in Hitachi Energy SuprOS, published on 28 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Default credentials vulnerability exists in SuprOS
product. If exploited, this could allow an authenticated
local attacker to use an admin account created during
product deployment.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2025-7740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7740 is a high-severity vulnerability in Hitachi Energy SuprOS, published on 28 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-7740 in the wild and no public exploit code.

Affected product: Hitachi Energy SuprOS. 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-7740/ (Markdown: https://insights.sbomify.com/CVE-2025-7740/index.md)
```

## Sources

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

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