# CVE-2026-24512: ingress-nginx auth-method nginx configuration injection

> Attackers can inject nginx configuration via Ingress paths, leading to arbitrary code execution and secret disclosure in the ingress-nginx controller.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 3 Feb 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-jx8c-56mg-h6vp, GO-2026-4426, MINI-29mf-w34v-3vj7, MINI-48qr-98vv-rgg5, MINI-5658-rv8h-2xh2, MINI-5c58-pvm4-x96m, MINI-5wmc-5rcx-fp67, MINI-66cq-j487-jx7v, MINI-gp62-3qc3-r33r, MINI-p64f-gh7r-35r7, MINI-v953-j98v-q245, MINI-xfm8-2jrp-h34w

## What is CVE-2026-24512?

CVE-2026-24512 is a high-severity code injection vulnerability in Kubernetes ingress-nginx, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security issue was discovered in ingress-nginx where the `rules.http.paths.path` Ingress field can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)

Weakness: CWE-20 (Improper Input Validation)

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

5 open source packages ship an affected version, including k8s.io/ingress-nginx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/ingress-nginx` | Go | All versions | None |
| `k8s.io/ingress-nginx` | Go | All versions | 1.13.7 |
| `k8s.io/ingress-nginx` | Go | All versions | 1.13.7 |
| `k8s.io/ingress-nginx` | Go | From 1.14.0 | 1.14.3 |
| `k8s.io/ingress-nginx` | Go | From 1.14.0 | 1.14.3 |

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

Upgrade k8s.io/ingress-nginx to a fixed version for your release line: 1.13.7 or 1.14.3.

## Is CVE-2026-24512 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24512 is a high-severity code injection vulnerability in Kubernetes ingress-nginx, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24512 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/ingress-nginx (Go): affected all versions; no fix listed
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.13.7
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.13.7
- k8s.io/ingress-nginx (Go): affected from 1.14.0; fixed in 1.14.3
- k8s.io/ingress-nginx (Go): affected from 1.14.0; fixed in 1.14.3

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

## Sources

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

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