CVE-2025-36194: IBM PowerVM Hypervisor · Improper Access Control for Register Interface
Affects IBM PowerVM HypervisorSource CVE Database V5
Not known to be exploited · CVSS 2.8 Low.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMPowerVM Hypervisor | Affected
| Fixed in– |
CPE configurations (12)
cpe:2.3:a:ibm:powervm_hypervisor:fw1110.00:*:*:*:*:*:*:*cpe:2.3:a:ibm:powervm_hypervisor:fw1110.00.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:powervm_hypervisor:fw1110.03:*:*:*:*:*:*:*cpe:2.3:a:ibm:powervm_hypervisor:fw1110.03.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:powervm_hypervisor:fw1060.00:*:*:*:*:*:*:*cpe:2.3:a:ibm:powervm_hypervisor:fw1060.00.0:*:*:*:*:*:*:*
AI-suggested
European organizations should implement the following specific mitigations: 1) Apply IBM patches or firmware updates as soon as they become available to address CVE-2025-36194. 2) Restrict and monitor shared processor configurations, limiting their use to trusted partitions only. 3) Enforce strict access control policies and segmentation between partitions to minimize the risk of data leakage. 4) Conduct regular audits of partition configurations and inter-partition communication to detect anomalous data flows. 5) Employ enhanced logging and monitoring on hypervisor management interfaces to identify potential exploitation attempts. 6) Limit administrative access to hypervisor management consoles and ensure multi-factor authentication is in place. 7) Educate system administrators about the risks of shared processor configurations and the importance of applying security updates promptly. 8) Consider isolating highly sensitive workloads on dedicated physical resources if feasible to eliminate shared processor risks.
Description
IBM PowerVM Hypervisor FW1110.00 through FW1110.03, FW1060.00 through FW1060.51, and FW950.00 through FW950.F0 may expose a limited amount of data to a peer partition in specific shared processor configurations during certain operations.