# CVE-2025-1098: ingress-nginx controller - configuration injection via unsanitized mirror annotations

> Attackers can inject arbitrary nginx configuration via unsanitized mirror annotations, leading to 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:** 24 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-vg63-w3p9-jc9m, GO-2025-3568, MINI-4fqr-hxgc-f7x6, MINI-4g73-6j37-whpq, MINI-5wgg-qm6w-pcwc, MINI-5xqr-vmqm-7pmx, MINI-7x44-88gp-wvq7, MINI-85c7-8xp2-jhr7, MINI-fpgp-2j4j-c4wf, MINI-jgc8-xqrq-ch42, MINI-wr68-73h2-m5r3, MINI-xgm9-jvr2-qfmg

## What is CVE-2025-1098?

CVE-2025-1098 is a high-severity code injection vulnerability in kubernetes ingress-nginx, published on 24 Mar 2025. 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 https://github.com/kubernetes/ingress-nginx  where the `mirror-target` and `mirror-host` Ingress annotations can be used to inject arbitrary 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-2025-1098?

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.11.5 |
| `k8s.io/ingress-nginx` | Go | All versions | 1.11.5 |
| `k8s.io/ingress-nginx` | Go | From 1.12.0-beta.0 | 1.12.1 |
| `k8s.io/ingress-nginx` | Go | From 1.12.0-beta.0 | 1.12.1 |

## How do I fix CVE-2025-1098?

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

## Is CVE-2025-1098 being exploited?

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

Public exploit code:

- Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE (exploitdb)
- Ingress-Nginx Controller - Configuration Injection via Unsanitized Mirror Annotations (nuclei): http/cves/2025/CVE-2025-1098.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1098 and fix it if it is affected.

What it is: CVE-2025-1098 is a high-severity code injection vulnerability in kubernetes ingress-nginx, published on 24 Mar 2025. 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-2025-1098 exists.

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.11.5
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.11.5
- k8s.io/ingress-nginx (Go): affected from 1.12.0-beta.0; fixed in 1.12.1
- k8s.io/ingress-nginx (Go): affected from 1.12.0-beta.0; fixed in 1.12.1

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

## Sources

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

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