CyberSecBulletin
CVE-2026-17414NVD status: Analyzed

IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80…

Published Updated By the CyberSecBulletin desk

CVE-2026-17414 is a high-severity improper input validation vulnerability in PowerVM Hypervisor from IBM, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected PowerVM Hypervisor versions: FW1120.00; FW1110.00 through FW1110.30; FW1060.00 through FW1060.80, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.3% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Power System S1122 (9824-22a) Firmware to fw1110.31 or a later version.
  2. Update Power System S1124 (9824-42a) Firmware to fw1110.31 or a later version.
  3. Update Power System S1122s (9824-22b) Firmware to fw1110.31 or a later version.
  4. Read the advisory on ibm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
IBMPowerVM HypervisorFW1120.00; FW1110.00 through FW1110.30; FW1060.00 through FW1060.80; FW950.00 through FW950.H2Not stated
IBMPower System S1122 (9824-22a) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System S1124 (9824-42a) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System S1122s (9824-22b) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System S1114 (9824-41b) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System L1122 (9856-22h) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System L1124 (9856-42h) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System E1150 (9043-mru) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System S1112 (9242-21b) Firmwarefw1120.00Not stated
IBMPower System S1112 (9242-21t) Firmwarefw1120.00Not stated
IBMPower System E1080 (9080-hex) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System S1022 (9105-22a) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System S1024 (9105-42a) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System S1022s (9105-22b) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System S1014 (9105-41b) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System L1022 (9786-22h) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System L1024 (9786-42h) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System E1050 (9043-mrx) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System S1012 (9028-21b) Firmwarefw1060.00 up to, but not including, fw1060.81fw1060.81
IBMPower System E1180 (9080-heu) Firmwarefw1110.00 up to, but not including, fw1110.31; fw1120.00fw1110.31
IBMPower System S922 (9009-22g) Firmwarefw950.00 up to, but not including, fw950.h3fw950.h3
IBMPower System H922 (9223-22s) Firmwarefw950.00 up to, but not including, fw950.h3fw950.h3
IBMPower System S914 (9009-41g) Firmwarefw950.00 up to, but not including, fw950.h3fw950.h3
IBMPower System S924 (9009-42g) Firmwarefw950.00 up to, but not including, fw950.h3fw950.h3
IBMPower System H924 (9223-42s) Firmwarefw950.00 up to, but not including, fw950.h3fw950.h3

Version data comes from the organisation that assigned the CVE; 2 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.1HighCNA (us.ibm.com)
CVSS 3.18.8HighNVD

Official description

IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 Power Systems Firmware is affected by a vulnerability in partition firmware during network boot. An unauthenticated attacker with access to the same network as a partition performing a network boot can prevent that partition from completing its boot sequence. On partitions where OS secure boot is not enabled, which is the default configuration, the attacker can also substitute the boot image, compromising everything subsequently loaded by that partition. Other partitions and the managed system are not affected. Only partitions actively performing a network boot are affected, resulting in a confidentiality, integrity, and availability impact.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in PowerVM Hypervisor

All PowerVM Hypervisor vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.