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.)
Metrics
Affected Vendors & Products
No data.
No data.
No data.
No data.
References
| Link | Providers |
|---|---|
| https://github.com/kubernetes/kubernetes/issues/136789 |
|
History
Fri, 06 Feb 2026 04:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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.) | |
| Title | ingress-nginx auth-proxy-set-headers nginx configuration injection | |
| Weaknesses | CWE-20 | |
| References |
| |
| Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: kubernetes
Published:
Updated: 2026-02-06T03:13:51.717Z
Reserved: 2026-02-05T23:44:40.775Z
Link: CVE-2025-15566
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-02-06T04:15:51.960
Modified: 2026-02-06T04:15:51.960
Link: CVE-2025-15566
Redhat
No data.
OpenCVE Enrichment
No data.