Cross-tenant data disclosure via skipped node cleaning
Published Aug 14, 2026 · Updated Aug 14, 2026
Data exposure in OpenStack Ironic 32.0.0 through 35.0.1 and 36.0.0 through 38.0.0 allows remote authenticated users to read prior tenant data. When a node is enrolled with or changed to autodetect, the deploy-interface transition is not preserved through cleaning, so automated disk erasure can be skipped. An authenticated tenant must receive such a node before another cleaning cycle; the bounded consequence is disclosure of residual storage data.
Summary
What happened
Data exposure in OpenStack Ironic 32.0.0 through 35.0.1 and 36.0.0 through 38.0.0 allows remote authenticated users to read prior tenant data. When a node is enrolled with or changed to autodetect, the deploy-interface transition is not preserved through cleaning, so automated disk erasure can be skipped. An authenticated tenant must receive such a node before another cleaning cycle; the bounded consequence is disclosure of residual storage data.
The record
- CVE
- CVE-2026-74250
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- OpenStack
- Product
- Ironic
- Classifications
- CWE-226, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 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=32.0.0 <35.0.2
- Affected versionversion=36.0.0 <38.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