Authenticated denial of service via checksum loop
Published May 14, 2026 · Updated May 14, 2026
Denial of service in OpenStack Ironic allows remote authenticated users to exhaust conductor threads via crafted deployment requests. Image handling calculates a missing checksum for a file:// source before validating that the source is a regular file, so /dev/zero never reaches EOF and occupies a conductor thread. An authenticated user authorized to write node.instance_info and deploy a node can repeat the request until the thread pool is exhausted, interrupting provisioning until the service restarts.
Summary
What happened
Denial of service in OpenStack Ironic allows remote authenticated users to exhaust conductor threads via crafted deployment requests. Image handling calculates a missing checksum for a file:// source before validating that the source is a regular file, so /dev/zero never reaches EOF and occupies a conductor thread. An authenticated user authorized to write node.instance_info and deploy a node can repeat the request until the thread pool is exhausted, interrupting provisioning until the service restarts.
The record
- CVE
- CVE-2026-44919
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- OpenStack
- Product
- Ironic
- Classifications
- CWE-696, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 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 <a3f6d735ac3642ab95b49142c7305f072ae748d0
What conditions does exploitation require?
What is affected?
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
- Crafted file:///dev/zero deployment requestproof of concept · demonstrated
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