Firmware BMC/FSP flaw lets attackers with BMC service/root access fully control host and all partitions on enterprise IBM Power Systems.
CVE-2026-17429
BMC/FSP vuln allows BMC-root users to control host and all partitions.
Is CVE-2026-17429 being exploited?
Not confirmed. CVE-2026-17429 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.10% probability of exploitation in the next 30 days.
How severe is CVE-2026-17429?
CVE-2026-17429 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-17429?
Yes. A fix has been recorded for CVE-2026-17429. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17429 affect?
CVE-2026-17429 affects IBM Power Systems FW1120.00, FW1110.00 - FW1110.30, FW1060.00 - FW1060.80, FW950.00 - FW950.H2, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17429?
Isolate BMC network, revoke/rotate BMC creds, restrict service accounts, monitor, and apply vendor firmware updates when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with BMC/FSP service or root can write hardware control registers, leading to full host and partition compromise (confidentiality, integrity, availability).
Immediate action required
- affectedFW1120.00
- affected>= FW1110.00 and <= FW1110.30
- affected>= FW1060.00 and <= FW1060.80
- affected>= FW950.00 and <= FW950.H2
- affected>= OP940.00 and <= OP940.a1
- affected>= OP940.00 and <= OP940.81
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.