# CVE-2026-71201: Missing authorization in Ironic

> A project reader can access Portgroups belonging to other projects via crafted requests, leading to unauthorized data disclosure.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-71201, GHSA-x4h6-wf22-px84, UBUNTU-CVE-2026-71201

## What is CVE-2026-71201?

CVE-2026-71201 is a medium-severity missing authorization vulnerability in OpenStack Ironic, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenStack Ironic through 38.0.0, a project reader that makes a crafted request to Ironic can return Portgroups assigned to Nodes owned or leased by another project.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-71201?


## How do I fix CVE-2026-71201?

Apply the vendor's patch.

## Is CVE-2026-71201 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71201 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71201 and fix it if it is affected.

What it is: CVE-2026-71201 is a medium-severity missing authorization vulnerability in OpenStack Ironic, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71201 exists.

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-71201/ (Markdown: https://insights.sbomify.com/CVE-2026-71201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71201
- OSV: https://osv.dev/vulnerability/CVE-2026-71201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71201/
Summaries are generated and may contain mistakes; the official description above is the record.