Skip to content
Cloud

CVE-2026-54423

HIGH
High
EPSS 0.30%Patch availableJul 10, 2026

Authenticated users can send arbitrary IPMI commands via Ironic, bypassing access controls

common questions

Is CVE-2026-54423 being exploited?

Not confirmed. CVE-2026-54423 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.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-54423?

CVE-2026-54423 is rated High. 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-54423?

Yes. A fix has been recorded for CVE-2026-54423. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54423 affect?

CVE-2026-54423 affects OpenStack Ironic < 37.0.1, OpenStack deployments using IPMI-managed bare-metal nodes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54423?

Upgrade Ironic to 37.0.1+, restrict deployer roles and limit IPMI network access

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenStack Ironic < 37.0.1OpenStack deployments using IPMI-managed bare-metal nodes
impact

Authenticated deployers can execute arbitrary IPMI commands on nodes, enabling power control, firmware/OS tampering, or full system compromise.

action required

Patch when possible

affected versions
OpenStack Ironic
  • affected>= 22.1.0 and < 29.0.6
  • affected>= 30.0.0 and < 32.0.2
  • affected>= 32.0.0 and < 35.0.2
  • affected>= 36.0.0 and < 37.0.1

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free