CVE-2026-54423
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn OpenStack Ironic before 37.0.1, an Ironic user with the ability to deploy nodes using the IPMI management interface can maliciously use the send_raw step to send arbitrary IPMI commands to a node, bypassing Ironic's access control.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenStack Ironic before version 37.0.1 contains an access control bypass where users with permissions to deploy nodes via the IPMI management interface can abuse the send_raw step to send arbitrary IPMI commands to physical hardware, circumventing Ironic's built-in authorization controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ironic versionRun 'ironic --version' or check the package version via 'pip show ironic' or your distribution's package managerAffected if The installed version is lower than 37.0.1 (e.g., 37.0.0, 36.x.x, or earlier)
-
Verify IPMI driver is enabledCheck Ironic configuration file (usually /etc/ironic/ironic.conf) for the 'enabled_drivers' setting, or run 'ironic driver list' to see active driversAffected if IPMI driver (ipmi) appears in the enabled drivers list
-
Identify nodes using IPMI managementRun 'ironic node-list' and for each node check 'ironic node-show <uuid>' looking for 'ipmi' in the 'management_interface' or 'driver' fieldAffected if Any node is configured to use IPMI for hardware management
-
Confirm send_raw step availabilityInspect the Ironic conductor logs or configuration for the presence of the 'send_raw' deploy step. Check /etc/ironic/ironic.conf or the Python ironic libraries for the send_raw step definitionAffected if The send_raw step is present and loadable in the Ironic deployment pipeline
-
Review user deploy permissions on IPMI nodesUse OpenStack identity service (keystone) to list role assignments: 'openstack role assignment list --role <deploy_role>' and cross-reference with users having access to IPMI-managed nodesAffected if Users with deploy permissions exist and IPMI-managed nodes are in use
You are affected if you run any Ironic version before 37.0.1 and have IPMI-managed nodes with the send_raw step available to users who have deploy permissions on those nodes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Ironic to version 37.0.1 or later. Until upgraded, restrict node deployment permissions on IPMI-managed nodes and audit user activity for unauthorized IPMI command usage.
OpenStack Ironic 37.0.1 or later
- Identify the current version of OpenStack Ironic currently deployed
- Upgrade OpenStack Ironic to version 37.0.1 or later
- After upgrading, verify that the send_raw command is now properly restricted by Ironic's access control policies
- Confirm that users with deploy capability can no longer send arbitrary IPMI commands through the send_raw step
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54423 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data