cve.bz

CVE-2026-89419 openstack ironic: Improper Protection of Alternate Path

5.0 mediumEPSS 0.3%

Medium (5.0) in openstack ironic. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
OpenStack Ironic before 39.0.1 sometimes allows a user to change the maintenance setting on a node via PATCH to /v1/nodes/{ident} - in other words, not using the specific maintenance endpoint.

Severity

CVSS 3.1

5.0 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-424 Improper Protection of Alternate Path
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-89419 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89419?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89419?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-89419 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-89419

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-89419](https://cve.bz/cve/badge/CVE-2026-89419.svg)](https://cve.bz/cve/CVE-2026-89419)

HTML:

<a href="https://cve.bz/cve/CVE-2026-89419"><img src="https://cve.bz/cve/badge/CVE-2026-89419.svg" alt="CVE-2026-89419"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenStack Ironicfrom 17.0.0 before 29.1.1
OpenStack Ironicfrom 30.0.0 before 32.1.1
OpenStack Ironicfrom 33.0.0 before 35.1.1
OpenStack Ironicfrom 36.0.0 before 39.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13ironicno fix listedDEBIAN-CVE-2026-89419
Debian14ironic1:39.0.0-6DEBIAN-CVE-2026-89419
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moreironicno fix listedUBUNTU-CVE-2026-89419

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Moderate because an authenticated project member who already has general node update access can toggle maintenance through the PATCH API (PR:L under default Ironic policy) without going through the dedicated maintenance endpoints that enforce stricter roles. Practical impact is mild: the main effect is operational inconvenience, including blocking power management and workflow request actions on the node until maintenance is cleared. There is no confidentiality impact and no arbitrary code execution.

The attack path applies where OpenStack Ironic is used with Keystone and project-scoped RBAC, including Red Hat OpenStack Platform and deployments that run OpenStack on OpenShift with that authorization model. OpenShift Container Platform does not use OpenStack Keystone or project-scoped lessee RBAC in any configuration; the described privilege gap does not apply to default OpenShift bare-metal Ironic in the same way. The issue remains relevant for customers deploying OpenStack on OpenShift and for RHOSP environments that grant project members general node update access.

Red Hat's mitigation

There is no practical operational or policy workaround for this issue. Upgrade to a fixed Ironic build when available. Until a fix is applied, maintenance toggled through this path can block power management and workflow request actions on affected nodes until maintenance is cleared by a user with appropriate access.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4openshift4/ose-ironic-rhel9Fix deferred
Red Hat OpenShift Container Platform 4openstack-ironicFix deferred
Red Hat OpenStack Platform 13 (Queens)openstack-ironicFix deferred
Red Hat OpenStack Platform 16.2openstack-ironicFix deferred
Red Hat OpenStack Platform 17.1openstack-ironicFix deferred
Red Hat OpenStack Platform 18.0openstack-ironicFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-89419.

Attack patterns (CAPEC)

  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium
  • CAPEC-554 Functionality Bypass Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON