CVE-2026-89419 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
Medium 5.0
Published
Updated
Check this codebase for CVE-2026-89419 and fix it if it is affected.
What it is: CVE-2026-89419 is a medium-severity vulnerability in OpenStack Ironic, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-89419 in the wild and no public exploit code.
Affected product: OpenStack Ironic. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-89419/ (Markdown: https://insights.sbomify.com/CVE-2026-89419/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-89419?
CVE-2026-89419 is a medium-severity vulnerability in OpenStack Ironic, published on 23 Oct 2026.
Official description
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.
Weakness: CWE-424
Which versions are affected by CVE-2026-89419?
How do I fix CVE-2026-89419?
No fix has been published for CVE-2026-89419 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-89419 being exploited?
There is no known exploitation of CVE-2026-89419 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-89419, GHSA-6x3j-5f9q-7h4j, UBUNTU-CVE-2026-89419.