Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain service processor credentials
-
DeliveryAccess IBM Power service processor interface
-
ExploitCraft malformed firmware update image
-
InstallSubmit image through update mechanism
-
C2Trigger stack buffer overflow in boot image validation
-
ExecuteExecute arbitrary code at service processor privilege
-
ImpactCompromise host system integrity
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an account with service access to the IBM Power service processor - this is the explicit prerequisite stated in the CVE description. This typically means access to the Hardware Management Console (HMC), Intelligent Platform Management Interface (IPMI), or equivalent IBM service channel at a high-privilege level, consistent with PR:H in the CVSS vector. The attack is delivered via a crafted code update image supplied through the firmware update mechanism during or triggering the host boot process image validation path. Exploitation is limited to: (1) accounts holding service processor credentials at an administrative level, (2) systems running one of the three specified firmware trains (FW1120.00, FW1110.x, FW1060.x), and (3) environments where the firmware update interface is reachable. Default installations with properly secured, network-isolated BMC/service processor management interfaces significantly constrain the attack surface. |
| Impact | The CVSS 8.2 score reflects a scope-changed, high-impact vulnerability (C:H/I:H/A:H) but is moderated by AV:L and PR:H - physical or privileged service access is required, significantly narrowing the exploitable population. The scope change metric is the most consequential signal here: code executed via the service processor can subvert host-level security controls including secure boot and hypervisor integrity, making this a firmware-level implant vector. No EPSS data was provided, and the absence of KEV listing and public POC suggests exploitation has not been observed at scale; however, the attack profile - a trusted insider or compromised service account with BMC/service processor access - aligns with advanced persistent threat and supply chain attack patterns. Even a mid-sized enterprise IT operation in radom hypothetically running IBM Power infrastructure should treat this as urgent given the persistence and stealth potential of firmware-level compromise, even though real-world exploitation probability for most environments is constrained by the PR:H prerequisite. CVSS indicates local vector consistent with the description's service processor access requirement - no conflict detected. |
| Exploit ScenarioDerived | An attacker who has compromised a service account with IBM Power service processor access - either through credential theft, insider threat, or lateral movement from an HMC management host - crafts a malformed firmware update image that triggers a stack-based buffer overflow in the image validation routine. The overflow redirects execution to attacker-supplied shellcode running at service processor privilege level, from which the attacker can implant persistent firmware backdoors or manipulate host boot integrity, surviving OS reinstallation. No public POC is known at this time. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 19, 2026
Arbitrary code execution on IBM Power host systems is possible when an attacker with service processor access supplies a maliciously crafted firmware update image that bypasses boot-time image validation. Affected firmware versions span three release trains: FW1120.00, FW1110.00-FW1110.30, and FW1060.00-FW1060.80. Exploitation yields full confidentiality, integrity, and availability impact on the host, with scope change indicating the compromise extends beyond the service processor itself. No public exploit or CISA KEV listing is identified at this time.
RemediationAI
The primary remediation is to apply IBM's firmware update as detailed in the vendor advisory at https://www.ibm.com/support/pages/node/7283221. An exact patched firmware version number is not independently confirmed from the available data - consult the advisory directly for the target firmware build. As a compensating control prior to patching, restrict service processor network access to dedicated, isolated management VLANs and enforce multi-factor authentication on all service accounts with BMC or HMC access; this reduces the practical exploitability given the PR:H requirement. Audit all accounts with service processor credentials and rotate them. Enabling firmware image signature verification policies where supported may provide additional defense, though the vulnerability specifically targets the validation path and may bypass such controls depending on implementation.
Affected VersionsENISA
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 Power systems use a service processor (an out-of-band management controller analogous to IPMI/BMC) that governs firmware updates and the host boot process. The vulnerability resides in the image validation path executed during firmware boot - the code responsible for verifying the integrity and authenticity of code update images. CWE-121 (Stack-based Buffer Overflow) identifies the root cause: a stack buffer can be overwritten by processing a crafted image, redirecting execution. Because the service processor operates at a privilege level below the host OS, successful exploitation achieves a scope change (S:C in the CVSS vector), meaning attacker-controlled code runs in a trust domain that can affect the host system independently of any OS-level defenses.
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
AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
PR:H confirmed by service processor access requirement; S:C reflects host system impact beyond the service processor; AV:L consistent with local/management-network access model.
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM Power Firmware FW1120.00, FW1110.00 through FW1110.30, and FW1060.00 through FW1060.80 is affected by a vulnerability in the host firmware boot process image validation path. An attacker with service access to the service processor can supply a maliciously crafted code update image, allowing arbitrary code to be executed on the host system. Successful exploitation could result in a confidentiality, integrity, and availability impact to the affected host system.
Executive ViewAI
A high-severity vulnerability in IBM Power firmware allows complete system compromise when an attacker with service processor access uploads a maliciously crafted firmware image that bypasses boot-time validation. This affects multiple firmware versions across three release trains, and puts critical data centers at risk of total infrastructure breach. Organizations running affected Power systems must immediately restrict service processor access and implement interim controls pending vendor remediation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict service processor access via role-based access control and require multi-factor authentication; (2) Implement mandatory dual-control procedures for all firmware update operations; (3) Establish firmware image provenance verification using external integrity checks independent of the affected device's validation engine; (4) Deploy continuous monitoring and alerting on service processor login attempts and administrative actions; (5) Isolate service processor network traffic via dedicated VLAN with egress-only access; (6) Require physical presence for firmware updates in addition to digital authorization. Monitor IBM advisory channels weekly for patch availability.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
IBM Flexible Service Processor (FSP) FW860.00 through FW860.B3, FW950.00 through FW950.C0, FW1030.00 through FW1030.61,
IBM PowerVM Hypervisor across four active firmware release trains is vulnerable to arbitrary Hostboot memory read and wr
Root-level attackers inside an IBM PowerVM logical partition can corrupt the partition firmware runtime boot configurati
Denial of service in IBM PowerVM Hypervisor firmware affects logical partitions running affected FW1120, FW1110, FW1060,
Local root access inside a guest logical partition (LPAR) on IBM PowerVM systems running affected partition firmware all
Improper handling of sensitive data in the IBM PowerVM Hypervisor partition resource dump interface allows an authentica
EUVD-2026-62674
GHSA-gxcw-mv6h-cx89
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB