dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-44918

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenStack Ironic through before 37.0.1 allows creation or modification of nodes cross-project without authorization.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenStack Ironic before version 37.0.1 lacks proper authorization checks when creating or modifying bare metal nodes, allowing authenticated users to create or modify nodes in projects they do not belong to. This cross-project authorization bypass enables users to manipulate infrastructure resources outside their intended project scope.

MitigationUpgrade OpenStack Ironic to version 37.0.1 or later to obtain the patched code with proper cross-project authorization enforcement. Additionally, review existing node allocations and audit project membership to identify any unauthorized modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine OpenStack Ironic version
    Run 'openstack baremetal version' or check the Ironic service version via package manager (e.g., 'rpm -q openstack-ironic' or 'dpkg -l | grep ironic'). If using Python client, run 'pip show python-ironicclient' and note the version string.
    Affected if Version is below 37.0.1 (e.g., 37.0.0, 36.x.x, or earlier)
  2. Confirm Ironic API service is running
    Check the Ironic API process status via systemctl (systemctl status ironic-api) or verify the API port 6385 is listening (netstat -tlnp | grep 6385 or ss -tlnp | grep 6385).
    Affected if Ironic API service is active and listening for connections
  3. Identify authenticated user access
    Review Keystone authentication configuration for Ironic in /etc/ironic/ironic.conf or via OpenStack service token settings. Check if non-admin users can obtain tokens via 'openstack token issue'.
    Affected if Regular (non-admin) project users can authenticate and obtain tokens through Keystone
  4. Inspect node ownership in Ironic
    Run 'openstack baremetal node list --all-projects' (if admin) to list nodes across all projects, or review Ironic database tables (nodes, conductors) for project_uuid fields that differ from the creating user's project.
    Affected if Nodes exist where project_uuid differs from the user's default project, indicating potential cross-project manipulation

If OpenStack Ironic version is below 37.0.1 and the Ironic API is accessible to authenticated non-admin users, the cross-project authorization bypass vulnerability is present in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenStack Ironic to version 37.0.1 or later to obtain the patched code with proper cross-project authorization enforcement. Additionally, review existing node allocations and audit project membership to identify any unauthorized modifications.

Recommended fix High confidence

OpenStack Ironic 37.0.1 or later

  1. 1. Identify the current installed version of OpenStack Ironic in your environment
  2. 2. Plan maintenance window for the upgrade
  3. 3. Backup Ironic database and configuration files
  4. 4. Upgrade OpenStack Ironic to version 37.0.1 or later
  5. 5. Verify the upgrade completed successfully
  6. 6. Test node creation and modification across projects to confirm authorization controls are enforced
  7. 7. Monitor logs for any authorization-related errors
Caveat Review OpenStack Ironic 37.0.1 release notes for any API or configuration changes that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44918 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data