Skip to main content
View

Attack ChainAIDerived

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

  1. Recon
    Obtain service processor credentials
  2. Delivery
    Access IBM Power service processor interface
  3. Exploit
    Craft malformed firmware update image
  4. Install
    Submit image through update mechanism
  5. C2
    Trigger stack buffer overflow in boot image validation
  6. Execute
    Execute arbitrary code at service processor privilege
  7. Impact
    Compromise 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.

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

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

Power Firmware FW1110.00 ≤FW1110.30
Power Firmware FW1120.00
Power Firmware FW1060.00 ≤FW1060.80

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

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

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.

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 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

Why It Matters

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.

Business Impact: Severe
Compensating Controls

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

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche enterprise hardware, IBM Power-specific deployment
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
Very 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.

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.

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