# CVE-2026-66138: Command injection in Ironic Python Agent

> A manager-role user can execute arbitrary code on Ironic Python Agent by injecting commands via the ntp_server configuration value.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-66138, GHSA-wj9f-vqw7-855c, UBUNTU-CVE-2026-66138

## What is CVE-2026-66138?

CVE-2026-66138 is a high-severity command injection vulnerability in OpenStack Ironic Python Agent, published on 24 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In OpenStack Ironic Python Agent through 11.6.0, a project-scoped user with the manager role can achieve arbitrary code execution on a running Ironic-Python-Agent via a maliciously constructed configuration, because the value of ntp_server is passed to a shell.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

Apply the vendor's patch.

## Is CVE-2026-66138 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66138 is a high-severity command injection vulnerability in OpenStack Ironic Python Agent, published on 24 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66138 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-66138/ (Markdown: https://insights.sbomify.com/CVE-2026-66138/index.md)
```

## Sources

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

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