dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2025-7386

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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
Information exposure vulnerability in Hitachi Storage Navigator. This issue affects Hitachi Virtual Storage Platform 5100, 5200, 5500, 5600, 5100H, 5200H, 5500H, 5600H, VX8: before DKCMAIN Ver. 90-09-24-00/00, SVP Ver. 90-09-24/00, before DKCMAIN Ver. 90-08-86-00/00, SVP Ver. 90-08-86/00; Hitachi Virtual Storage Platform G1000, G1500, F1500, VX7: before DKCMAIN Ver. 80-06-96-00/00, SVP Ver. 80-06-91/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 · moderate confidence

Information exposure vulnerability in Hitachi Storage Navigator affecting multiple Virtual Storage Platform models (5100, 5200, 5500, 5600, G1000, G1500, F1500, and VX7/8 variants). The vulnerability allows unauthorized disclosure of sensitive information due to missing or insufficient security controls in the Storage Navigator component before specified version thresholds.

MitigationUpgrade DKCMAIN firmware and SVP (Service Processor) software to the versions specified (DKCMAIN Ver. 90-09-24-00/00 or 90-08-86-00/00 for 5x00H series; DKCMAIN Ver. 80-06-96-00/00 for G1000/G1500/F1500/VX7) to remediate the information exposure.

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

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 the Virtual Storage Platform model
    Access the Storage Navigator interface or check system documentation to determine if the deployed model is one of: 5100, 5200, 5500, 5600, G1000, G1500, F1500, or VX7/8 variants
    Affected if The model is any of the listed VSP models (5100, 5200, 5500, 5600, G1000, G1500, F1500, VX7/8)
  2. Verify Storage Navigator component is in use
    Confirm that the Storage Navigator management component is deployed and accessible on the storage system. Storage Navigator is the GUI/CLI tool used to manage Hitachi VSP arrays
    Affected if Storage Navigator is used to manage the VSP array
  3. Check DKCMAIN firmware version for 5x00H series
    Access the storage system maintenance terminal or Storage Navigator and retrieve the DKCMAIN firmware version. For 5x00H series models, compare the version against: 90-09-24-00/00 or 90-08-86-00/00
    Affected if DKCMAIN version is earlier than 90-09-24-00/00 or 90-08-86-00/00 on 5x00H series models
  4. Check DKCMAIN firmware version for G1000/G1500/F1500/VX7
    Access the storage system maintenance terminal or Storage Navigator and retrieve the DKCMAIN firmware version. For G1000/G1500/F1500/VX7 models, compare against: 80-06-96-00/00
    Affected if DKCMAIN version is earlier than 80-06-96-00/00 on G1000/G1500/F1500/VX7 models
  5. Check SVP software version
    Locate the Service Processor (SVP) software version through Storage Navigator system information or SVP management interface. Note: The SVP version should be checked in conjunction with DKCMAIN firmware versions
    Affected if SVP software version is not at the recommended level corresponding to the patched DKCMAIN firmware

A system is affected if it uses Storage Navigator to manage any of the listed VSP models and has DKCMAIN firmware version below the specified thresholds for its model family.

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 DKCMAIN firmware and SVP (Service Processor) software to the versions specified (DKCMAIN Ver. 90-09-24-00/00 or 90-08-86-00/00 for 5x00H series; DKCMAIN Ver. 80-06-96-00/00 for G1000/G1500/F1500/VX7) to remediate the information exposure.

Recommended fix High confidence

DKCMAIN Ver. 90-09-24-00/00 / SVP Ver. 90-09-24/00 for VSP 5100/5200/5500/5600 series; DKCMAIN Ver. 80-06-96-00/00 / SVP Ver. 80-06-91/00 for VSP G1000/G1500/F1500/VX7

  1. Identify your specific Hitachi Virtual Storage Platform model (VSP 5100, 5200, 5500, 5600, 5100H, 5200H, 5500H, 5600H, VX8, G1000, G1500, F1500, or VX7)
  2. Check the current DKCMAIN and SVP firmware versions currently installed on your system
  3. For VSP 5100/5200/5500/5600/5100H/5200H/5500H/5600H/VX8: Upgrade to DKCMAIN Ver. 90-09-24-00/00 or later and SVP Ver. 90-09-24/00 or later
  4. For VSP G1000/G1500/F1500/VX7: Upgrade to DKCMAIN Ver. 80-06-96-00/00 or later and SVP Ver. 80-06-91/00 or later
  5. Verify the upgrade was successful by checking the firmware versions post-installation
Caveat Firmware upgrades on storage arrays typically require planned downtime and should be thoroughly tested in a non-production environment first; ensure adequate backups exist before performing upgrades

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7386 — 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-7386 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