# CVE-2026-94572: Code injection in Octavia

> Authenticated users can inject HAProxy directives via TLS ciphers in OpenStack Octavia Amphora deployments, potentially leading to code execution.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 21 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-94572, GHSA-xwpf-r3rp-gx2r, UBUNTU-CVE-2026-94572

## What is CVE-2026-94572?

CVE-2026-94572 is a critical code injection vulnerability in OpenStack Octavia, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenStack Octavia before 18.0.1, the Amphora provider driver did not validate the listener and pool tls_ciphers field for control characters. The value is written verbatim into the HAProxy configuration generated on the amphora, and thus an authenticated project member who owns a TLS-enabled load balancer can embed a newline and inject arbitrary HAProxy configuration directives. Only deployments using the Amphora provider are affected.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

Upgrade to a fixed version.

## Is CVE-2026-94572 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94572 is a critical code injection vulnerability in OpenStack Octavia, published on 21 Sep 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-94572 exists.

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

## Sources

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

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