CVE-2025-44021

OpenStack Ironic before 29.0.1 can write unintended files to a target node disk during image handling (if a deployment was performed via the API). A malicious project assigned as a node owner can provide a path to any local file (readable by ironic-conductor), which may then be written to the target node disk. This is difficult to exploit in practice, because a node deployed in this manner should never reach the ACTIVE state, but it still represents a danger in environments running with non-default, insecure configurations such as with automated cleaning disabled. The fixed versions are 24.1.3, 26.1.1, and 29.0.1.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2025-44021 has a CVSS score of 2.8 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (24.1.3, 26.1.1, 29.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-44021? CVE-2025-44021 is a low-severity path traversal vulnerability in ironic (pip), affecting versions < 24.1.3. It is fixed in 24.1.3, 26.1.1, 29.0.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2025-44021? CVE-2025-44021 has a CVSS score of 2.8 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ironic are affected by CVE-2025-44021? ironic (pip) versions < 24.1.3 is affected.
4. Is there a fix for CVE-2025-44021? Yes. CVE-2025-44021 is fixed in 24.1.3, 26.1.1, 29.0.1. Upgrade to this version or later.
5. Is CVE-2025-44021 exploitable, and should I be worried? Whether CVE-2025-44021 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-44021 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-44021?
   • Upgrade ironic to 24.1.3 or later
   • Upgrade ironic to 26.1.1 or later
   • Upgrade ironic to 29.0.1 or later