Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Ironic API is network-accessible; PR:H because operator privileges are required; S:C because iSCSI credential leakage impacts storage systems outside Ironic; I:N and A:N because only information disclosure occurs.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Lifecycle Timeline
1DescriptionCVE.org
In OpenStack Ironic through 35.0.1, when applying a PATCH to update fields in volume properties the user is authorized for, Ironic can return unredacted sensitive information (such as iSCSI credentials). The PATCH outcome is a security issue; the POST outcome is not a security issue.
AnalysisAI
Unredacted iSCSI credential disclosure in OpenStack Ironic through 35.0.1 occurs specifically when an authenticated operator issues a PATCH request to update authorized fields in a node's volume properties - the API response returns sensitive data such as iSCSI CHAP usernames and secrets in plaintext. The scope change reflected in the CVSS (S:C) is meaningful: leaked storage credentials extend the blast radius beyond Ironic itself to the underlying iSCSI storage infrastructure. Notably, the same volume properties endpoint does not exhibit this behavior on POST requests, isolating the flaw to the PATCH response serialization path. No public exploit code has been identified and the vulnerability is not listed in CISA KEV.
Technical ContextAI
OpenStack Ironic is a bare-metal provisioning service that manages physical nodes and can attach block storage volumes using protocols such as iSCSI, which require authentication credentials (CHAP username and secret). The CPE cpe:2.3:a:openstack:ironic:*:*:*:*:*:*:*:* confirms all Ironic versions through 35.0.1 are affected. The root cause is CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer): the PATCH handler for volume connector or volume target records returns the full resource representation after a field update without scrubbing sensitive credential fields, even though the same data is correctly redacted in POST responses. This asymmetry between HTTP verbs in the response serialization logic is the precise technical defect.
RemediationAI
Upgrade OpenStack Ironic to a version beyond 35.0.1 once a patched release is published; monitor the Launchpad bug report at https://bugs.launchpad.net/ironic/+bug/2155049 for fix confirmation and exact patched version, as no specific fixed release was confirmed in the available input data. As a compensating control while awaiting a patch, restrict PATCH access to Ironic volume connector and volume target API endpoints to the minimum required set of service accounts using OpenStack's oslo.policy RBAC rules - this reduces the number of identities that can trigger the disclosure. Audit existing API access logs for unexpected PATCH requests to volume properties endpoints, which may indicate prior credential harvesting. Rotate iSCSI CHAP credentials for any nodes whose volume properties have been modified via PATCH since the Ironic deployment was stood up. Note that restricting PATCH permissions may break legitimate automation workflows that dynamically update volume configurations and would require coordination with operations teams.
Arbitrary file overwrite in OpenStack Ironic (bare-metal provisioning service) lets an authenticated tenant supply a cra
Boot script injection in OpenStack Ironic versions up to and including 35.0.x allows authenticated tenants to influence
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
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 Information Disclosure
View allVendor StatusVendor
Debian
Bug #1140012| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye | vulnerable | 1:16.0.3-1 | - |
| bookworm | vulnerable | 1:21.1.0-3 | - |
| bookworm (security) | vulnerable | 1:21.4.4-0+deb12u1 | - |
| trixie | vulnerable | 1:29.0.0-7 | - |
| trixie (security) | vulnerable | 1:29.0.5-0+deb13u2 | - |
| forky, sid | vulnerable | 1:35.0.1-5 | - |
| (unstable) | fixed | (unfixed) | - |
SUSE
Severity: ModerateShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36658
GHSA-j4cw-mcg2-2q78