<Vulnerability name="CVE-2026-44918">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Important</ThreatSeverity>
    <PublicDate>2026-07-08T15:00:00</PublicDate>
    <Bugzilla id="2494664" url="https://bugzilla.redhat.com/show_bug.cgi?id=2494664" xml:lang="en:us">
openstack-ironic: Prevent rehoming resources to nodes with different owner
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>8.7</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-1220</CWE>
    <Details xml:lang="en:us" source="Mitre">
OpenStack Ironic through before 37.0.1 allows creation or modification of nodes cross-project without authorization.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in OpenStack Ironic. An authenticated project manager can change the node associated with Volume Connectors or Volume Target objects, potentially changing the project permitted to access the object. Volume Connectors contain secrets in environments configuring boot from volume with iSCSI volumes. Additionally, a project manager with the ability to create nodes can use the UUID of a node not owned by their project as a parent node when creating a new node. This mismatched child node can then be used to impact operations on the parent, such as forcing it to power on.
    </Details>
    <Statement xml:lang="en:us">
The Red Hat Product Security team has assessed the severity of this vulnerability as Important. An authenticated project manager can reparent Volume Connectors and Volume Targets to nodes in a different project, crossing project authorization boundaries and potentially exposing iSCSI secrets used for boot-from-volume configurations. However, exploitation requires the 'manager' role, which is not a default role in OpenStack and must be explicitly granted by an administrator. The attacker must also know the UUID of the target node in the other project. In Red Hat OpenStack Platform 18.0, the automatic_lessee feature defaults to false and did not function correctly; a properly working version was only introduced in upstream release 26.1.0 (gazpacho), which Red Hat does not ship. The parent/child node relationship capability, introduced in upstream Ironic 22.0.0, has never been shipped in any version of Red Hat OpenStack Platform or Red Hat OpenStack Services on OpenShift. These factors reduce the practical attack surface in Red Hat shipped configurations.
    </Statement>
    <Mitigation xml:lang="en:us">
Operators who are concerned they may have had this occur are encouraged to perform a basic audit of node configuration, for instance, ensuring the expected number of volume targets and volume connectors are present. Operators can also use the provided ironic-status upgrade check to identify misconfigured nodes.
    </Mitigation>
    <PackageState cpe="cpe:/a:redhat:openshift:4">
        <ProductName>Red Hat OpenShift Container Platform 4</ProductName>
        <FixState>Affected</FixState>
        <PackageName>openstack-ironic</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:openstack:16.2">
        <ProductName>Red Hat OpenStack Platform 16.2</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>openstack-ironic</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:openstack:17.1">
        <ProductName>Red Hat OpenStack Platform 17.1</ProductName>
        <FixState>Affected</FixState>
        <PackageName>openstack-ironic</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:openstack:18.0">
        <ProductName>Red Hat OpenStack Platform 18.0</ProductName>
        <FixState>Affected</FixState>
        <PackageName>openstack-ironic</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-44918
https://nvd.nist.gov/vuln/detail/CVE-2026-44918
https://launchpad.net/bugs/2150256
https://launchpad.net/bugs/2150450
    </References>
</Vulnerability>