dbcve.org
Virtual Storage One BlockApplication · Hitachi

CVE-2025-9661

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OS command injection vulneravility in the management gui (maintenance utility) of Hitachi Virtual Storage Platform One Block 23, 24, 26 and 28. This issue affects Hitachi Virtual Storage Platform One Block 23/24/26/28: before DKCMAIN A3-04-21-40/00, ESM A3-04-21/00.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS command injection vulnerability in the management GUI maintenance utility of Hitachi Virtual Storage Platform One Block storage systems (models 23, 24, 26, and 28). The vulnerability allows unauthenticated or authenticated attackers to execute arbitrary operating system commands on the storage array through the maintenance interface.

MitigationUpgrade Hitachi VSP One Block to DKCMAIN version A3-04-21-40/00 or later, and ESM version A3-04-21/00 or later to patch the command injection flaw.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Virtual Storage One BlockApplication
Affected:= 23= 24= 26= 28

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your VSP One Block model
    Access the storage system management interface or use system inventory commands to confirm the model number is 23, 24, 26, or 28
    Affected if The model number is 23, 24, 26, or 28 - these are the affected models
  2. Check DKCMAIN firmware version
    Use the maintenance or system information interface to retrieve the installed DKCMAIN version number
    Affected if The DKCMAIN version is below A3-04-21-40/00 (versions prior to this patch contain the vulnerability)
  3. Check ESM firmware version
    Use the maintenance or system information interface to retrieve the installed ESM version number
    Affected if The ESM version is below A3-04-21/00 (versions prior to this patch contain the vulnerability)
  4. Verify management GUI maintenance utility exposure
    Determine if the management GUI maintenance utility is network-accessible or exposed to untrusted networks
    Affected if The maintenance utility is accessible without proper network segmentation or authentication controls

You are affected if you run a VSP One Block model 23, 24, 26, or 28 with DKCMAIN version before A3-04-21-40/00 or ESM version before A3-04-21/00, and the management GUI maintenance interface is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Hitachi VSP One Block to DKCMAIN version A3-04-21-40/00 or later, and ESM version A3-04-21/00 or later to patch the command injection flaw.

Recommended fix High confidence

DKCMAIN A3-04-21-40/00 and ESM A3-04-21/00 or later

  1. Contact Hitachi support or access the official Hitachi support portal to obtain the firmware update
  2. Download the DKCMAIN firmware version A3-04-21-40/00 or later
  3. Download the ESM firmware version A3-04-21/00 or later
  4. Follow Hitachi's documented firmware update procedure for Virtual Storage Platform One Block (typically through the maintenance utility in the management GUI)
  5. Verify the update was successful and the vulnerability is resolved
Caveat No specific breaking changes mentioned in the advisory; however, always test updates in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Virtual Storage One Block Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9661 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data