Openstack Ironic
10 CVEs affecting Openstack Ironic. Latest disclosed: 2026-06-05. Critical: 0, High: 1.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2026-42997 | High | 7.7 | 2026-05-05 | An issue was discovered in idrac in OpenStack Ironic before 35.0.1. During import, a user invoking molds can request authorization to be sent to a remote endpo… |
CVE-2026-42510 | Medium | 6.6 | 2026-04-28 | OpenStack Ironic before 35.0.1 allows ipmitool execution in a non-default configuration that has a console interface. |
CVE-2015-7514 | Medium | 6.5 | 2017-06-07 | OpenStack Ironic 4.2.0 through 4.2.1 does not "clean" the disk after use, which allows remote authenticated users to obtain sensitive information. |
CVE-2026-48681 | Medium | 5.9 | 2026-06-04 | OpenStack Ironic through before 35.0.2 allows file overwrite via directory traversal during deployment with a crafted ISO image. |
CVE-2026-46447 | Medium | 5.8 | 2026-06-03 | OpenStack Ironic before 35.0.2 allows Boot Script Injection of an iPXE script if the attacker can set node.driver_info or node.instance_info. |
CVE-2026-50589 | Medium | 5.3 | 2026-06-05 | In OpenStack Ironic 32 through 35.0.1, an unauthenticated malicious user could submit a crafted JSON string to some endpoints on the API or JSON-RPC service an… |
CVE-2026-44917 | Medium | 4.9 | 2026-06-04 | OpenStack Ironic before 35.0.2 allows a malicious authenticated project admin or manager to read local files on the Ironic conductor via a pxe_template. |
CVE-2026-44919 | Medium | 4.3 | 2026-05-14 | In OpenStack Ironic through 35.x before a3f6d73, during image handling, an infinite loop in checksum calculations can occur via the file:///dev/zero URL. |
CVE-2026-44916 | Low | 3.0 | 2026-05-08 | In OpenStack Ironic before 35.0.2 (in a certain non-default configuration), instance_info['ks_template'] is rendered without sandboxing. |
CVE-2025-44021 | Low | 2.8 | 2025-05-08 | 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… |