Skip to main content
VulnerabilityPublished Updated

CVE-2025-5781: Hitachi Ops Center API Configuration Manager · Sensitive Data in Logs

Affects Hitachi Ops Center API Configuration ManagerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.2 Medium : upgrade to 11.0.5-00 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.0.5-00, 8.6.5-00
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Hitachi to 11.0.5-00 (Ops Center API Configuration Manager, Configuration Manager) or 8.6.5-00 (Device Manager).

Affected software

ProductAffectedFixed in
HitachiHitachi Ops Center API Configuration ManagerAffected
  • >=10.0.0-00 <11.0.5-00
Fixed in
  • 11.0.5-00
HitachiHitachi Configuration ManagerAffected
  • >=8.5.1-00 <11.0.5-00
Fixed in
  • 11.0.5-00
HitachiHitachi Device ManagerAffected
  • >=8.4.1-00 <8.6.5-00
Fixed in
  • 8.6.5-00

AI-suggested

To mitigate CVE-2025-5781, organizations should: 1) Apply vendor patches or updates as soon as Hitachi releases versions 11.0.5-00 or later that address this vulnerability. 2) Review and harden logging configurations to ensure sensitive session tokens, credentials, or personally identifiable information are not recorded in logs. This may involve disabling verbose logging or implementing log filtering and redaction mechanisms. 3) Restrict access to log files strictly to authorized personnel and systems, using file system permissions and network controls to limit exposure. 4) Monitor logs for unusual access patterns or attempts to retrieve sensitive information. 5) Employ network segmentation and strong access controls to reduce the risk of local or adjacent network attackers gaining access to management systems or logs. 6) Conduct regular security audits and penetration tests focusing on log management and session security in Hitachi management environments. 7) Educate administrators about the risks of sensitive data exposure in logs and best practices for secure session management.

Description

Information Exposure Vulnerability in Hitachi Ops Center API Configuration Manager, Hitachi Configuration Manager, Hitachi Device Manager allows Session Hijacking.This issue affects Hitachi Ops Center API Configuration Manager: from 10.0.0-00 before 11.0.5-00; Hitachi Configuration Manager: from 8.5.1-00 before 11.0.5-00; Hitachi Device Manager: from 8.4.1-00 before 8.6.5-00.

References

Community reviews

Loading reviews…