CVE-2026-42997: An issue was discovered in idrac in OpenStack Ironic before 35.0.1.
An issue was discovered in idrac in OpenStack Ironic before 35.0.1. During import, a user invoking molds can request authorization to be sent to a remote endpoint. The credential forwarded is a time-limited Keystone token (which provides access to all OpenStack services Ironic is authorized for); or basic credentials configured for molds storage. The fixed versions are 26.1.6, 29.0.5, 32.0.1, and 35.0.1.
Security readout for executives and security teams
Plain-English summary
This flaw can leak sensitive OpenStack credentials when an authorized user triggers a specific Ironic iDRAC import workflow. The leaked token is time-limited but may let an attacker access every OpenStack service that Ironic can access. Basic credentials for molds storage may also be exposed.
Executive priority
Treat as high priority for OpenStack environments running Ironic. The main business risk is credential exposure that may broaden access across cloud services authorized to Ironic.
Technical view
OpenStack Ironic before fixed releases mishandles authorization forwarding during idrac molds import. A low-privileged authenticated user can cause credentials to be sent to a remote endpoint. Impact is confidentiality only, with scope change, high confidentiality impact, and no integrity or availability impact in the CVSS vector.
Likely exposure
Exposure is most likely in OpenStack Ironic deployments using affected versions and the idrac molds import path, especially where non-administrative users can invoke molds imports.
Exploitation context
The source bundle does not show KEV listing or cited active exploitation. Exploitation requires low privileges, network access, and no user interaction, but depends on access to the relevant Ironic import capability.
Researcher notes
Evidence supports CWE-201 and CWE-669: credentials cross trust boundaries during idrac molds import. The bundle names fixed upstream versions but does not include exploit details or independent exploitation reports.
Mitigation direction
Upgrade Ironic to 26.1.6, 29.0.5, 32.0.1, 35.0.1, or later fixed versions.
Check OpenStack and distribution vendor advisories for packaged update availability.
Restrict access to idrac molds import functions until fixed.
Review and rotate exposed Keystone tokens or molds storage credentials if compromise is suspected.
Validation and detection
Inventory OpenStack Ironic versions across controllers and bare-metal services.
Confirm deployments are on a listed fixed version or vendor-patched equivalent.
Identify whether idrac molds import is enabled or exposed to non-administrative users.
Review recent imports for unexpected remote endpoints receiving authorization material.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.