IBM Power Systems are widely used in enterprise datacenters; firmware RCE can fully compromise host systems and disrupt operations.
CVE-2026-96263
IBM Power Systems firmware flaw allows arbitrary code via malicious update image.
Is CVE-2026-96263 being exploited?
Not confirmed. CVE-2026-96263 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.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-96263?
CVE-2026-96263 is rated High with a CVSS score of 8.2. 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-96263?
Not known from our data. No patch reference has been recorded for CVE-2026-96263, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-96263 affect?
CVE-2026-96263 affects IBM Power Systems FW1120.00 - FW1120.01, IBM Power Systems FW1110.00 - FW1110.31, IBM Power Systems FW1060.00 - FW1060.81. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-96263?
Restrict service-processor access, apply IBM firmware updates when released, and monitor for suspicious activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Service-processor access allows supplying a crafted firmware update enabling arbitrary code execution on the host, leading to full system compromise (CIA).
Immediate action required
- affected>= FW1120.00 and <= FW1120.01
- affected>= FW1110.00 and <= FW1110.31
- affected>= FW1060.00 and <= FW1060.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.