CVE-2026-48681

The ironic-api service in OpenStack Ironic before 4.2.5 (Liberty) and 5.x before 5.1.2 (Mitaka) allows remote attackers to obtain sensitive information about a registered node by leveraging knowledge of the MAC address of a network card belonging to that node and sending a crafted POST request to the v1/drivers/$DRIVER_NAME/vendor_passthru resource.

In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.

In OpenStack Ironic through 38.0.0, a project reader making a crafted request can return Portgroups assigned to Nodes owned or leased by another project.

In OpenStack Ironic before version 37.0.1, a user with the ability to deploy nodes via the IPMI management interface can maliciously use the send_raw step to send arbitrary IPMI commands to a node, bypassing Ironic's access control.

A vulnerability in OpenStack Ironic before version 37.0.1 allows unauthorized creation or modification of nodes across projects. Lack of proper authorization enables an attacker to manipulate resources without required permissions.

In OpenStack Ironic before version 37.0.1, when applying a PATCH to update fields in volume properties the user is authorized for, Ironic can return unredacted sensitive information (such as iSCSI credentials).

In OpenStack Ironic versions 32 through 37.0.0, an unauthenticated user can submit a crafted JSON string to some API or JSON-RPC endpoints, causing a service crash.

OpenStack Ironic before 35.0.2 allows a malicious authenticated project admin or manager to read local files on the Ironic conductor via a pxe_template.

OpenStack Ironic before 35.0.2 allows iPXE script injection if the attacker can set node.driver_info or node.instance_info.

In OpenStack Ironic versions up to 35.x before a3f6d73, during image handling, an infinite loop in checksum calculations can occur via the file:///dev/zero URL.