dbcve.org
Configuration ManagerApplication · Hitachi

CVE-2025-0976

HIGH · 7.5 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 8.6.1-00 / 11.0.4-00 or later.
See remediation →
84/100
Remediation priority · High
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
Information Exposure Vulnerability in Hitachi Ops Center API Configuration Manager, Hitachi Configuration Manager.This issue affects Hitachi Ops Center API Configuration Manager: from 10.0.0-00 before 11.0.4-00; Hitachi Configuration Manager: from 8.6.1-00 before 11.0.5-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

An information exposure vulnerability in Hitachi Ops Center API Configuration Manager and Hitachi Configuration Manager allows unauthorized access to sensitive data. The vulnerability exists in versions prior to the fixed releases (11.0.4-00 for API Configuration Manager, 11.0.5-00 for Configuration Manager).

MitigationUpgrade to Hitachi Ops Center API Configuration Manager version 11.0.4-00 or later, or Hitachi Configuration Manager version 11.0.5-00 or later to remediate this information exposure vulnerability.

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
Configuration ManagerApplication
Affected:< 8.6.1-00>= 8.6.1-00, < 11.0.5-00
Ops Center Api Configuration ManagerApplication
Affected:>= 10.0.0-00, < 11.0.4-00

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 if Hitachi Configuration Manager is installed
    Check for installation directories or use system inventory tools to find Hitachi Configuration Manager software
    Affected if The product is installed and version is below 11.0.5-00 (or below 8.6.1-00)
  2. Identify if Hitachi Ops Center API Configuration Manager is installed
    Check for installation directories or use system inventory tools to find Hitachi Ops Center API Configuration Manager software
    Affected if The product is installed and version is 10.0.0-00 or higher but below 11.0.4-00
  3. Determine the installed version of Hitachi Configuration Manager
    Query the product's version information through its administrative interface, command line, or version file in the installation directory
    Affected if Version is less than 11.0.5-00 (including any version below 8.6.1-00)
  4. Determine the installed version of Hitachi Ops Center API Configuration Manager
    Query the product's version information through its administrative interface, command line, or version file in the installation directory
    Affected if Version is 10.0.0-00 or higher but less than 11.0.4-00
  5. Check if the API Configuration Manager web interface is accessible
    Attempt to access the product's API endpoints or web console to confirm it is running and reachable
    Affected if The vulnerable product version is running and exposed on the network

You are affected if either Hitachi Configuration Manager below version 11.0.5-00 or Hitachi Ops Center API Configuration Manager between versions 10.0.0-00 and 11.0.4-00 is installed and running.

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
Upgrade available Upgrade to 8.6.1-00 / 11.0.4-00 / 11.0.5-00 or later
Fixed in 8.6.1-0011.0.4-0011.0.5-00
Interim mitigation

Upgrade to Hitachi Ops Center API Configuration Manager version 11.0.4-00 or later, or Hitachi Configuration Manager version 11.0.5-00 or later to remediate this information exposure vulnerability.

Recommended fix High confidence

Hitachi Ops Center API Configuration Manager 11.0.4-00 or later; Hitachi Configuration Manager 11.0.5-00 or later

  1. Identify which Hitachi product is affected: Ops Center API Configuration Manager or Configuration Manager
  2. For Hitachi Ops Center API Configuration Manager (versions 10.0.0-00 through 11.0.3-00): upgrade to version 11.0.4-00 or later
  3. For Hitachi Configuration Manager (versions 8.6.1-00 through 11.0.4-00): upgrade to version 11.0.5-00 or later
  4. Obtain the upgrade from official Hitachi channels or support portal
  5. Apply the upgrade following Hitachi's standard upgrade procedures
  6. Verify the fix by confirming sensitive information is no longer written to logs

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

Fix this in Configuration Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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