EUVD-2026-34181
GHSA-jrh2-f5jc-xpgr
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Ironic API is network-reachable and requires a low-privilege tenant account (AV:N/AC:L/PR:L); injected boot script crosses to the provisioned node (S:C) tampering integrity only, with no data disclosure or DoS.
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Lifecycle Timeline
9Description PRE-NVD
AnalysisAI
Boot script injection in OpenStack Ironic versions up to and including 35.0.x allows authenticated tenants to influence boot scripts processed by the bare-metal provisioning service, with integrity impact extending across a CVSS scope change to the provisioned hardware. Confirmed by upstream advisory OSSA-2026-017 and an Ubuntu USN, with no public exploit identified at time of analysis and an EPSS of 0.03% indicating no observed exploitation activity.
Technical ContextAI
Ironic is the OpenStack bare-metal provisioning service that orchestrates iPXE/PXE boot, image deployment, and lifecycle management of physical nodes. CWE-669 (Incorrect Resource Transfer Between Spheres) here manifests as content originating from a less-trusted sphere (tenant-controlled input or node-supplied data) being incorporated into the boot script that Ironic hands to a bare-metal node, crossing the trust boundary between the API/control plane and the firmware/boot environment of the physical host. The affected CPE is openstack:ironic across all versions through the 35.0.x branch, and the vulnerability lives in the path where Ironic constructs the boot configuration delivered over the provisioning network.
RemediationAI
Patch available per vendor advisory: apply the Ironic update referenced in OSSA-2026-017 (https://security.openstack.org/ossa/OSSA-2026-017.html) and, on Ubuntu, install the packages from USN-8421-1 (https://ubuntu.com/security/notices/USN-8421-1); exact fix versions are not enumerated in the supplied intelligence, so consult the OSSA stable-branch backport list before deploying. Until patched, compensating controls include restricting Ironic API access to trusted operators only (tighten Keystone roles so tenants cannot reach node-management endpoints), isolating the provisioning network so untrusted nodes cannot inject content consumed during boot, and reviewing any custom deploy templates or driver_info fields that flow into boot scripts - the trade-off is reduced self-service provisioning for tenants and additional operational friction when onboarding new hardware.
Arbitrary file overwrite in OpenStack Ironic (bare-metal provisioning service) lets an authenticated tenant supply a cra
Credential forwarding vulnerability in OpenStack Ironic's idrac driver allows authenticated attackers to steal time-limi
Denial of service in OpenStack Ironic versions 32 through 35.0.1 allows remote unauthenticated attackers to crash the ba
Command injection via ipmitool in OpenStack Ironic through 25.0.0 allows authenticated operators with high privileges to
Unredacted iSCSI credential disclosure in OpenStack Ironic through 35.0.1 occurs specifically when an authenticated oper
OpenStack Ironic 4.2.0 through 4.2.1 does not "clean" the disk after use, which allows remote authenticated users to obt
Infinite loop denial-of-service in OpenStack Ironic's image handling allows low-privileged authenticated attackers to ex
Cross-tenant information disclosure in OpenStack Ironic before 38.0.1 exposes residual disk contents from prior bare met
Incorrect authorization in OpenStack Ironic through 38.0.0 allows an authenticated low-privilege project reader to leak
File extraction from the Ironic conductor service is possible via a crafted pxe_template, as disclosed in OpenStack Secu
Server-side template injection in OpenStack Ironic through version 35.x allows authenticated administrators to disclose
Same technique Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today