# CVE-2025-2514: Improper Restriction of Excessive Authentication Attempts vulnerability in Hitachi Virtual Storage Platform

> Attackers can bypass authentication restrictions on Hitachi Virtual Storage Platforms, potentially leading to unauthorized access and account takeover.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-6g2f-5j4g-w6f4

## What is CVE-2025-2514?

CVE-2025-2514 is a medium-severity authentication bypass vulnerability in Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper restriction of excessive authentication attempts vulnerability in Hitachi Virtual Storage Platform G130, G150, G350, G370, G700, G900, F350, F370, F700, F900, Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H, Hitachi Virtual Storage Platform One Block 23, One Block 24, One Block 26, One Block 28.

This issue affects Hitachi Virtual Storage Platform G130, G150, G350, G370, G700, G900, F350, F370, F700, F900, Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H, Hitachi Virtual Storage Platform One Block 23, One Block 24, One Block 26, One Block 28  : before DKCMAIN Ver 88-08-16-xx/00, GUM Ver. 88-08-20/00, before DKCMAIN Ver 93-07-26-xx/00, GUM Ver. 93-07-26/00, before DKCMAIN Ver A3-04-02-xx/00, EMS Ver. A3-04-02/00, before DKCMAIN Ver A3-03-41-xx/00, EMS Ver. A3-03-41/00, before DKCMAIN Ver A3-03-03-xx/00, EMS Ver. A3-03-02/00.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 20 products.


Products: Hitachi Virtual Storage One Block, Hitachi Vsp E1090 Firmware, Hitachi Vsp E1090h Firmware, Hitachi Vsp E390 Firmware, Hitachi Vsp E390h Firmware, Hitachi Vsp E590 Firmware, Hitachi Vsp E590h Firmware, Hitachi Vsp E790 Firmware, Hitachi Vsp E790h Firmware, Hitachi Vsp E990 Firmware, Hitachi Vsp F350 Firmware, Hitachi Vsp F370 Firmware, Hitachi Vsp F700 Firmware, Hitachi Vsp F900 Firmware, Hitachi Vsp G130 Firmware, Hitachi Vsp G150 Firmware, Hitachi Vsp G350 Firmware, Hitachi Vsp G370 Firmware, Hitachi Vsp G700 Firmware, Hitachi Vsp G900 Firmware.

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

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

## Is CVE-2025-2514 being exploited?

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

## Other vulnerabilities in Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H

- [CVE-2025-1978](https://insights.sbomify.com/CVE-2025-1978/): Remote Code Execution Vulnerability in Hitachi Storage Navigator and the maintenance console (high 8.3)
- [CVE-2025-9661](https://insights.sbomify.com/CVE-2025-9661/): Command injection in Hitachi Virtual Storage Platform One Block 23 (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2514 is a medium-severity authentication bypass vulnerability in Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H, published on 7 May 2026. 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-2514 in the wild and no public exploit code.

Affected product: Hitachi Virtual Storage Platform E390, E590, E790, E990, E1090, E390H, E590H, E790H, E1090H. 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-2514/ (Markdown: https://insights.sbomify.com/CVE-2025-2514/index.md)
```

## Sources

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

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