Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain FSP service-level credentials
  2. Delivery
    Connect to FSP management network interface
  3. Exploit
    Craft malformed mailbox message targeting Hostboot
  4. Install
    Trigger OOB memory read/write in Hostboot address space
  5. C2
    Corrupt host firmware boot stack
  6. Execute
    Load compromised hypervisor on reboot
  7. Impact
    Full hypervisor and guest workload compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires authenticated service-level access to the FSP (Flexible Service Processor) - a privilege tier that is distinct from and more restricted than standard OS-level or hypervisor-level administrative access. FSP service-level credentials are used for hardware diagnostics, firmware updates, and low-level system management, and are not exposed by default to ordinary system administrators. The CVSS vector confirms AV:L (local/management-network access to the FSP interface) and PR:H (high privilege - FSP service-level authentication). Systems where the FSP management network is isolated from untrusted networks and where FSP service-level credentials are individually assigned, audited, and rotated are at substantially reduced risk. Exploitation is not possible by an attacker with only OS-level root access or standard PowerVM administrator access; FSP service-level credentials must be separately compromised. Non-default FSP access controls and proper network segmentation are the primary limiting factors.

Impact

The CVSS 8.2 score with vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H accurately reflects the attack profile: local access vector (FSP management network), low complexity once credentials are obtained, and a high privilege prerequisite (FSP service-level authentication). The scope change to S:C is the key severity amplifier - exploiting the FSP mailbox to corrupt Hostboot memory enables hypervisor-level compromise, which in turn affects all guest workloads on the managed system. No EPSS score was provided, making quantitative exploitation probability unavailable. No CISA KEV listing indicates no confirmed active exploitation at time of analysis, and no POC is identified, reducing near-term automated exploitation risk. Real-world risk is concentrated in environments where FSP service-level credentials are shared across teams, reused, or where FSP management networks are not properly segmented - scenarios common in large-scale IBM POWER deployments. This is not a mass-exploitation-class vulnerability due to the PR:H prerequisite; however, insider threats, supply-chain actors, or post-breach lateral movement targeting IBM infrastructure management planes represent credible threat actors. The combination of firmware-level impact and full CIA compromise means recovery from exploitation would require complete firmware re-provisioning, making this a high-consequence, lower-frequency risk.

Exploit ScenarioDerived

An attacker who has obtained FSP service-level credentials - through credential theft from a shared service account, insider access, or compromise of an IBM management system - connects to the FSP management interface on a targeted POWER-series server. The attacker sends a specially crafted mailbox message designed to trigger an out-of-bounds read or write operation within Hostboot's memory space, corrupting the host firmware boot stack. On next system boot (or if the corruption affects live Hostboot memory), the hypervisor loaded from the tampered firmware inherits the compromise, granting the attacker persistent control over all virtual machines and workloads running on the managed system. No public POC has been identified, meaning this scenario currently requires knowledge of the FSP mailbox protocol internals.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 19, 2026

IBM PowerVM Hypervisor across four active firmware release trains is vulnerable to arbitrary Hostboot memory read and write via the FSP service processor mailbox interface, enabling compromise of the entire host firmware boot stack and the hypervisor subsequently loaded from it. An authenticated attacker holding FSP service-level credentials can send a specially crafted mailbox message that triggers an out-of-bounds memory operation (CWE-125), achieving full confidentiality, integrity, and availability impact against the managed POWER-series system. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the scope change to the hypervisor layer makes this a critical risk for IBM POWER environments with shared or exposed FSP credentials.

RemediationAI

The primary remediation is to apply vendor-supplied firmware updates for the affected release train in use - consult the IBM advisory at https://www.ibm.com/support/pages/node/7283235 for specific patched firmware versions per release train (FW1120, FW1110, FW1060, FW950), as exact fix versions were not included in the available data and must be obtained directly from IBM. As compensating controls where immediate firmware patching is not feasible: restrict FSP service-level access to the smallest possible set of named, individually accountable administrators and audit the FSP credential store to identify shared or stale accounts (note this may require changes to existing service workflows); isolate the FSP management network from general administrative and user networks using dedicated VLANs or physical separation, limiting which systems can initiate FSP connections; enable FSP access logging and alert on anomalous mailbox message patterns or unexpected service-level login events. Be aware that strict FSP network segmentation may impair legitimate remote management capabilities and should be coordinated with operations teams before implementation.

Affected VersionsENISA

PowerVM Hypervisor FW1060.00 ≤FW1060.80
PowerVM Hypervisor FW950.00 ≤FW950.H2
PowerVM Hypervisor FW1120.00
PowerVM Hypervisor FW1110.00 ≤FW1110.30

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IBM PowerVM is a Type-1 hypervisor deployed on IBM POWER-series enterprise servers. The FSP (Flexible Service Processor) is a dedicated out-of-band management processor responsible for hardware initialization, diagnostics, and remote management, operating independently of the host OS and hypervisor. Hostboot is IBM's open-source firmware layer that runs on the POWER host processor to initialize hardware before the hypervisor is loaded - it represents the root of the firmware trust chain. The vulnerability resides in the mailbox interface, an inter-processor communication mechanism between the FSP and the Hostboot layer. CWE-125 (Out-of-Bounds Read) is the NVD-assigned root cause class; however, the reporter's tags also include Buffer Overflow, indicating the crafted mailbox message may trigger both out-of-bounds reads and writes in Hostboot memory space. Compromising Hostboot memory gives an attacker control over the entire boot chain, meaning any hypervisor subsequently loaded inherits the compromise. The CVSS S:C (Scope Changed) metric captures this precisely: FSP-layer exploitation crosses the security boundary into the hypervisor domain. Affected firmware trains span FW950 through FW1120, covering a wide range of deployed POWER8/9/10-era hardware.

Know when Power System E1080 9080 Hex Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (us) PRIMARY 8.2 HIGH
AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.2 HIGH

FSP service-level authentication required (PR:H, AV:L); S:C reflects hypervisor compromise from a lower FSP security domain; full C/I/A justified by arbitrary Hostboot memory read/write.

3.1 AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (us).

CVSS VectorVendor: us

Attack Vector
Local
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the service processor mailbox interface. An attacker with authenticated service-level access to the FSP can send a specially crafted mailbox message to read or modify arbitrary regions of Hostboot memory, compromising the host firmware boot stack and the hypervisor subsequently loaded by it. Successful exploitation results in a confidentiality, integrity, and availability impact to the managed system.

Executive ViewAI

Why It Matters

IBM PowerVM Hypervisor firmware contains a critical memory read/write vulnerability affecting the Hostboot layer and entire hypervisor stack on POWER-series systems. Organizations with exposed FSP service processor credentials face direct risk of firmware compromise with complete loss of confidentiality, integrity, and availability. No patch is currently available, requiring immediate credential isolation and access controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict FSP service processor network access to isolated, out-of-band management VLANs only; (2) Implement mandatory multi-factor authentication on all FSP credential access; (3) Enable detailed audit logging for FSP mailbox interface communications with alerting on anomalous patterns; (4) Rotate all FSP service-level credentials immediately; (5) Disable FSP remote-access capability where operationally feasible, permitting local console access only; (6) Establish continuous monitoring for unexpected firmware modifications or abnormal boot sequences on POWER systems.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
IBM POWER enterprise servers, specialized high-end niche
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy