Credential disclosure via unredacted volume target response
Published Jun 14, 2026 · Updated Jun 14, 2026
Information disclosure in OpenStack Ironic before 37.0.1 allows remote authenticated users to read iSCSI credentials in volume target PATCH responses. The API RBAC response path returns the volume target properties object without applying the redaction that normally masks sensitive connection fields. A valid token and permission to send POST or PATCH requests to /v1/volume/targets are required; disclosure is limited to sensitive properties in the response.
Summary
What happened
Information disclosure in OpenStack Ironic before 37.0.1 allows remote authenticated users to read iSCSI credentials in volume target PATCH responses. The API RBAC response path returns the volume target properties object without applying the redaction that normally masks sensitive connection fields. A valid token and permission to send POST or PATCH requests to /v1/volume/targets are required; disclosure is limited to sensitive properties in the response.
The record
- CVE
- CVE-2026-54421
- Published
- Jun 14, 2026
- Updated
- Jun 14, 2026
- Vendor
- OpenStack
- Product
- Ironic
- Classifications
- CWE-212, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 2026CVE publishedPublication date reported by the CVE source.
- Jun 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=35.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo