# CVE-2025-1097: ingress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation

- Exploited (CISA KEV): no
- Published: 2025-03-24
- CVSS: 8.8 HIGH (v3.1)
- EPSS: 37.0% (99th percentile)
- CWE: CWE-20

A security issue was discovered in  ingress-nginx https://github.com/kubernetes/ingress-nginx  where the `auth-tls-match-cn` Ingress annotation 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.)

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | No public claim | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | No public claim | — | — |
| Fastly | Before feed history | — | — |
| F5 | Rule published | 2025-04-28 | 35 |
| Akamai | No public source | — | — |
| OWASP CRS | No public claim | — | — |

### F5

- 2025-04-28 · new · rule 200103569
  > Added: signature 200103569 "Kubernetes NGINX Ingress Admission Controller Command Execution" (Command Execution, risk High), systems: Nginx. References: CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24514.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog
- 2025-05-22 · new · rule 200103569
  > Added: signature 200103569 "Kubernetes NGINX Ingress Admission Controller Command Execution" (Command Execution, risk High), systems: Nginx. References: CVE-2025-1097, CVE-2025-1098, CVE-2025-1974, CVE-2025-24514.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog

## Our test (measured)

- OWASP Core Rule Set 4.25.0, paranoia level 1, anomaly threshold 5, default CRS settings: blocked (1 of 1 requests blocked), template CVE-2025-1097, 2026-11-02
- OWASP Core Rule Set 4.25.0, paranoia level 2, anomaly threshold 5, default CRS settings: blocked (1 of 1 requests blocked), template CVE-2025-1097, 2026-11-02

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2025-1097 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2025-1097