Unauthenticated remote code execution in IBM Power Systems firmware risks full compromise of enterprise servers and managed infrastructure used broadly across organizations.
CVE-2026-16687
Unauthenticated RCE in IBM Power Systems ASMI firmware
Is CVE-2026-16687 being exploited?
Not confirmed. CVE-2026-16687 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.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-16687?
CVE-2026-16687 is rated Critical with a CVSS score of 9.6. 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-16687?
Yes. A fix has been recorded for CVE-2026-16687. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16687 affect?
CVE-2026-16687 affects IBM Power Systems Firmware FW1120.00, IBM Power Systems Firmware FW1110.00 - FW1110.30, IBM Power Systems Firmware FW1060.00 - FW1060.80, IBM Power Systems Firmware FW950.00 - FW950.H2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16687?
Isolate ASMI/FSP management network, block management ports, and apply vendor firmware updates when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote arbitrary code execution via ASMI/FSP, enabling full control of managed Power Systems (confidentiality, integrity, availability loss).
Immediate action required
- affectedFW1120.00
- affected>= FW1110.00 and <= FW1110.30
- affected>= FW1060.00 and <= FW1060.80
- affected>= FW950.00 and <= FW950.H2
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.