Incorrect Permission Assignment for Critical Resource Vulnerability in HA Monitor
Affects HA Monitor versions 01-00 up to 01-77-02 on AIX, Linux or HP-IPF. The fix is in 01-77-02. The CVSS score is 7.3 (high), and no vendor severity rating is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 01-77-02
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. HA Monitor in the listed version ranges, on AIX, Linux or HP-IPF
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.13% · 2nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Incorrect Permission Assignment for Critical Resource Vulnerability in HA Monitor.
This issue affects HA Monitor: from 01-00 before 01-83-01.
Who should check
Teams running HA Monitor (Japanese or English version) on AIX, Linux or HP-IPF within the affected version ranges
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 7.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
HA Monitor in the listed version ranges, on AIX, Linux or HP-IPFUpgrade to a fixed version: 01-77-02.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-112125 (Incorrect Permission Assignment for Critical Resource Vulnerability in HA Monitor), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-112125 (entry last updated 2026-11-10): Affected: - Hitachi HA Monitor: from 01-00, fixed in 01-77-02 Fixed versions: 01-77-02. Conditions (all must be true for the bug to be hit): - HA Monitor in the listed version ranges, on AIX, Linux or HP-IPF (source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-163/index.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: local access, low-privilege login, a user action. CISA KEV: CVE-2026-112125 is not listed as of cve.now's last read. This KEV status is for CVE-2026-112125 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-163/index.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-112125 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-112125.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Hitachi HA Monitor
From 01-00 · fixed in 01-77-02
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112125
Is CVE-2026-112125 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug is an incorrect permission assignment for a critical resource in HA Monitor. The CVSS vector describes local access, low privileges and required user interaction, with high impact to confidentiality, integrity and availability.Source: hitachi.com
Which versions are affected by CVE-2026-112125?
HA Monitor: from 01-00 before 01-77-02.Source: cve.now feed data
Am I affected, and how do I check?
HA Monitor versions from 01-00 up to, but not including, 01-77-02 are listed as affected, on AIX, Linux or HP-IPF. To check, look at the installed HA Monitor version and the operating system it runs on.Source: hitachi.com
How do I fix CVE-2026-112125?
Upgrade HA Monitor to 01-77-02, which is the listed fixed version.Source: hitachi.com