CVE-2025-36035: IBM PowerVM Hypervisor · Unthrottled Resource Allocation
Affects IBM PowerVM HypervisorSource CVE Database V5
Not known to be exploited · CVSS 6.7 Medium.
Data as of 26 Oct 2026, 14:05 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:L/PR:H/UI:N/S:C/C:L/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Sep 2025
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 |
|---|---|---|
| IBM PowerVM Hypervisor | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-36035 effectively, European organizations should implement a multi-layered approach: 1) Restrict and monitor privileged access rigorously to ensure only authorized personnel can execute hypervisor-level commands, employing the principle of least privilege. 2) Implement strict auditing and logging of hypervisor calls and administrative actions to detect anomalous or suspicious activity early. 3) Use network segmentation and isolation to limit the exposure of systems running IBM PowerVM, reducing the risk of lateral movement by attackers. 4) Employ resource usage monitoring and alerting to identify unusual memory consumption patterns that could indicate exploitation attempts. 5) Maintain up-to-date backups and disaster recovery plans to minimize downtime in case of denial of service. 6) Engage with IBM support and subscribe to their security advisories to promptly apply patches or firmware updates once available. 7) Consider deploying additional security controls such as host-based intrusion detection systems (HIDS) tailored to detect hypervisor-level anomalies. 8) Conduct regular security training for administrators to recognize and prevent misuse of privileged access. These measures go beyond generic advice by focusing on hypervisor-specific controls and proactive monitoring tailored to the nature of this vulnerability.
Description
IBM PowerVM Hypervisor FW950.00 through FW950.E0, FW1050.00 through FW1050.50, and FW1060.00 through FW1060.40 could allow a local privileged user to cause a denial of service by issuing a specially crafted IBM i hypervisor call that would disclose memory contents or consume excessive memory resources.