OpenStack Ironic EUVD-2026-108574

Requires an authenticated low-privileged OpenStack Ironic API account able to invoke the vendor_passthru interface on a managed node, and the targeted node must be driven by a Redfish-based BMC so that DELETE and GET requests are proxied to the BMC's Redfish service (e.g., to delete BMC accounts). Affected deployments are OpenStack Ironic versions before 39.0.1. Exploitation is limited by the need for valid Ironic credentials (PR:L) and by the node being configured with a Redfish BMC; it is not reachable by a fully unauthenticated attacker.

This is a moderate-severity, authenticated authorization flaw (CWE-1287, improper validation of specified input type) rather than an urgent emergency. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, base 5.4) indicates a network-reachable attacker who already holds low-level privileges (PR:L) can, with low complexity and no user interaction, abuse the vendor_passthru mechanism to issue DELETE and GET operations - producing limited confidentiality and integrity impact. The vuln.today decision label is 'this_month', consistent with a medium issue that should be patched on a normal cycle rather than immediately. No EPSS score, no CISA KEV listing, and no exploit/PoC reference were provided - the two references are a Launchpad bug report and the OpenStack OSSA-2026-047 advisory (vendor sources, not exploit code). Signals are therefore internally consistent and point to a real-but-not-critical issue: the PR:L requirement meaningfully limits the attacker population to those with existing Ironic API access, and the most notable concern is lateral impact onto the BMC's Redfish service (e.g., deleting BMC accounts), which the base CVSS scope of S:U arguably understates. No active-exploitation or widespread-scanning data is available to elevate priority.

An actor with low-privileged but valid OpenStack Ironic API access targets a bare-metal node managed via a Redfish BMC driver and invokes vendor_passthru to proxy DELETE and GET requests through to the node's BMC Redfish service - for example deleting administrative accounts on the BMC. No public exploit was identified at time of analysis, and the attack requires existing authenticated access per the CVSS PR:L metric.