# CVE-2025-1718: Denial of service in Relion 670/650 and SAM600-IO

> An authenticated user with FTP access can cause a denial of service by triggering a device reboot through improper disk space management.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** GHSA-4435-f3hr-hpq3

## What is CVE-2025-1718?

CVE-2025-1718 is a high-severity denial of service vulnerability in Hitachi Energy Relion 670/650 and SAM600-IO, published on 24 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated user with file access privilege via FTP access can cause the Relion 670/650 and SAM600-IO series device to reboot due to improper disk space management.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2025-1718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1718 is a high-severity denial of service vulnerability in Hitachi Energy Relion 670/650 and SAM600-IO, published on 24 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1718 in the wild and no public exploit code.

Affected product: Hitachi Energy Relion 670/650 and SAM600-IO. 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-1718/ (Markdown: https://insights.sbomify.com/CVE-2025-1718/index.md)
```

## Sources

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

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