Authenticated file disclosure via unrestricted PXE template
Published Jun 4, 2026 · Updated Jun 4, 2026
File disclosure in OpenStack Ironic before 35.0.2 allows remote authenticated users to read conductor files via pxe_template. The boot interface accepts an unrestricted node.driver_info[pxe_template] path and publishes the conductor-readable file through TFTP or HTTP. Project owner or manager privileges to modify driver_info are required, and retrieval requires network access to the conductor's netboot service.
Summary
What happened
File disclosure in OpenStack Ironic before 35.0.2 allows remote authenticated users to read conductor files via pxe_template. The boot interface accepts an unrestricted node.driver_info[pxe_template] path and publishes the conductor-readable file through TFTP or HTTP. Project owner or manager privileges to modify driver_info are required, and retrieval requires network access to the conductor's netboot service.
The record
- CVE
- CVE-2026-44917
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- OpenStack
- Product
- Ironic
- Classifications
- CWE-669, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 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=17.0.0 <26.1.7
- Affected versionversion=27.0.0 <29.0.6
- Affected versionversion=30.0.0 <32.0.2
- Affected versionversion=33.0.0 <35.0.2
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