CVE-2026-44916: OpenStack Ironic remote code execution in Anaconda deploy interface

CVE-2026-44916 · Severity: low · CVSS 3 · Published 2026-05-08

OpenStack Ironic, a service for managing bare metal hardware, contains a vulnerability in its Anaconda deployment interface. In specific non-default configurations, an authorized user could execute malicious code on the server managing the hardware. This could lead to a full compromise of the management infrastructure, including access to hardware credentials and the ability to manipulate server provisioning.

Technologies: OpenStack Ironic. Vendors: OpenStack.

Quick answers

Is CVE-2026-44916 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44916 being exploited in the wild.
How severe is CVE-2026-44916?
Low severity, with a CVSS score of 3, published 8 May 2026.
Which products and versions are affected?
OpenStack Ironic >=17.0.0 <26.1.7, >=27.0.0 <29.0.6, >=30.0.0 <32.0.2, >=33.0.0 <35.0.2.
Is there a fix for CVE-2026-44916?
A patch was published on 2026-05-11: Security advisory OSSA-2026-012 released with patches Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44916 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-44916?
Check whether you run OpenStack Ironic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Template Injection (SSTI) vulnerability exists in OpenStack Ironic's Anaconda deploy interface. The root cause is the use of an unsandboxed jinja2.Environment to render the 'ks_template' provided in instance_info. An attacker with permissions to modify node instance information can provide a URL to a malicious Jinja2 template, leading to remote code execution (RCE) within the ironic-conductor process. This affects deployments where the 'anaconda' interface is enabled in ironic.conf and assigned to nodes. The vulnerability is mitigated by switching to jinja2.sandbox.SandboxedEnvironment.

Affected products

  • OpenStack Ironic >=17.0.0 <26.1.7, >=27.0.0 <29.0.6, >=30.0.0 <32.0.2, >=33.0.0 <35.0.2

Timeline

  • 2026-04-14: disclosed: Bug reported to OpenStack security team
  • 2026-05-08: advisory: CVE published
  • 2026-05-11: patched: Security advisory OSSA-2026-012 released with patches

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.