Firmware vulnerability in IBM Power Systems that enables arbitrary host firmware code execution, impacting enterprise server infrastructure and datacenters.
CVE-2026-96264
FSP mailbox overflow allows arbitrary code execution in IBM Power Systems firmware.
Is CVE-2026-96264 being exploited?
Not confirmed. CVE-2026-96264 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-96264?
CVE-2026-96264 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-96264?
Not known from our data. No patch reference has been recorded for CVE-2026-96264, 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-96264 affect?
CVE-2026-96264 affects IBM Power Systems Firmware FW1060.00-FW1060.81, Flexible Service Processor (FSP), Managed host firmware/runtime. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-96264?
Restrict FSP access, rotate service credentials, audit FSP logs, apply vendor firmware updates when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated service-level access to the FSP enables arbitrary code execution in host firmware, full memory and hardware control (CIA).
Immediate action required
- 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.