# CVE-2026-54422: Information disclosure in Ironic Python Agent

> A malicious bootc container deployed via OpenStack Ironic Python Agent can extract the credentials used to download it.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-54422, GHSA-7r4g-5584-3hjx, UBUNTU-CVE-2026-54422

## What is CVE-2026-54422?

CVE-2026-54422 is a medium-severity vulnerability in OpenStack Ironic Python Agent, published on 24 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In OpenStack Ironic Python Agent through 11.5.0, a malicious bootc container, when deployed using ironic-python-agent, may be able to extract the credentials used to download it.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

Upgrade to a fixed version.

## Is CVE-2026-54422 being exploited?

There is no known exploitation of CVE-2026-54422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54422 is a medium-severity vulnerability in OpenStack Ironic Python Agent, published on 24 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54422 in the wild and no public exploit code.

Affected product: OpenStack Ironic Python Agent. 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-54422/ (Markdown: https://insights.sbomify.com/CVE-2026-54422/index.md)
```

## Sources

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

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