CVE-2026-44918

Public on

Last Modified: UTC

Important Important severity What does this mean?
8.7 CVSS v3 Score Breakdown

Description

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.

Statement

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.

Mitigation

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.

Additional information

External References

Affected Packages and Issued Red Hat Security Errata

Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Products / Services Components State Errata
Red Hat OpenShift Container Platform 4.19 openshift4/ose-ironic-rhel9 Fixed This content is not included.RHSA-2026:57408
Red Hat OpenShift Container Platform 4.2 openshift4/ose-ironic-rhel9 Fixed This content is not included.RHSA-2026:54583
Red Hat OpenShift Container Platform 4.21 openshift4/ose-ironic-rhel9 Fixed This content is not included.RHSA-2026:54602
Red Hat OpenShift Container Platform 4.22 openshift4/ose-ironic-rhel9 Fixed RHSA-2026:51038
Red Hat OpenStack Platform 13 (Queens) openstack-ironic Not affected
Red Hat OpenStack Platform 16.2 openstack-ironic Not affected
Red Hat OpenStack Platform 17.1 openstack-ironic Affected
Red Hat OpenStack Platform 18.0 openstack-ironic Affected

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown

Red Hat NVD cve.org
CVSS v3 Base Score 8.7 N/A 5.5
Attack Vector Network N/A Network
Attack Complexity Low N/A Low
Privileges Required High N/A High
User Interaction None N/A None
Scope Changed N/A Unchanged
Confidentiality Impact High N/A High
Integrity Impact High N/A Low
Availability Impact None N/A None

CVSS v3 Vector

Red Hat CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

cve.org CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Red Hat CVSS v3 Score Explanation

Scope changed from Unchanged to Changed per discussion with Julia Kreger (OpenStack Ironic PTL). The attacker operates within their own project but can access volume connectors and secrets belonging to a different project, crossing project authorization boundaries. PR kept as High per Julia: manager role is admin-scoped within project, and attacker needs UUID of target node (requiring access to the other project).

Acknowledgements

Upstream acknowledges Julia Kreger (OpenStack) as the original reporter.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.

My product is listed as "Out of Support Scope". What does this mean?

 When a product is listed as "Out of Support Scope", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase. The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed. The product should be assumed to be affected. Customers are advised to apply any mitigation options documented on this page, consider removing or disabling the impacted component, or upgrade to a supported version of the product that has an update available.