Repository navigation
Description
CVSS Rating: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) (Score: 9.8, Critical)
A security issue was discovered in Kubernetes where under certain conditions, an unauthenticated attacker with access to the pod network can achieve arbitrary code execution in the context of the ingress-nginx controller. This can lead to disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)
Am I vulnerable?
This issue affects ingress-nginx. If you do not have ingress-nginx installed on your cluster, you are not affected. You can check this by running `kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx`.
Affected Versions
- < v1.11.0
- v1.11.0 - 1.11.4
- v1.12.0
How do I mitigate this vulnerability?
ACTION REQUIRED: The following steps must be taken to mitigate this vulnerability: Upgrade ingress-nginx to v1.11.5, v1.12.1, or any later version.
Before applying the patch, this issue can be mitigated by disabling the Validating Admission Controller functionality of ingress-nginx.
Fixed Versions
- ingress-nginx main@0ccf4ca
To upgrade, refer to the documentation: Upgrading Ingress-nginx
Detection
There are no known indicators of compromise that prove this vulnerability has been exploited.
If you find evidence that this vulnerability has been exploited, please contact [email protected]
Acknowledgements
This vulnerability was reported by Nir Ohfeld, Ronen Shustin, Sagi Tzadik, and Hillai Ben Sasson from Wiz
The issue was fixed and coordinated by Marco Ebert, James Strong, Tabitha Sable, and the Kubernetes Security Response Committee
Activity
tabbysable commentedon Mar 23, 2025
/triage accepted
thisisharrsh commentedon Mar 24, 2025
Hi @tabbysable, Please add the issue description for better understanding of the issue.
/triage needs-information
[-]Placeholder Issue[/-][+]CVE-2025-1974: ingress-nginx admission controller RCE escalation[/+]tabbysable commentedon Mar 24, 2025
/area security
/kind bug
/committee security-response
/label official-cve-feed
/sig network
45 remaining items
Mr-P-D commentedon Mar 27, 2025
Based on the official comments from the Kubernetes Blog, PODs can only be accessed by the people/user in the same VPC/corporate network.
Hence, i think the Attack Vector parameter in CVSS Score should be Adjacent (A) and not Network, as this vulnerability is not remotely exploitable. External attacker cannot directly interact with PODs, making it impossible to exploit remotely.
Reference - https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/
tuminoid commentedon Mar 27, 2025
From the wiz.io blog:
Some folks publicly expose the admission controller, which warrants Network I believe 🤷
chore: Upgrade ingress-nginx to 4.12.1
chore: Upgrade ingress-nginx to 4.12.1
suhettfilipe commentedon Mar 28, 2025
I had an issue after the update. We were using version 1.10 and upgraded to 1.12.1, but we encountered a problem with our external ingress—some ingress hosts were returning 404. However, when we switched to 1.11.5, the issue was resolved. Do you know anything about this?
Edit: I found the problem here:
kubernetes/ingress-nginx#12655
CVE-2025-1974: add allow-snippet-annotations: true in nginx-ingress c…
ntavares commentedon Apr 1, 2025
Thanks @suhettfilipe indeed, version 1.12.1 seems to not be doing what this CVE or documentation is stating, it seems to discard ingresses with configuration/server -snippets, regardless of allow-snippet-annotations: true (
didn't check if annotations-risk-level: Critical will helpI decided to check this, from what I can see we need to use the configurations allow-snippet-annotations=true together with annotations-risk-level=Critical).This is particularly confusing because if the error is introduced after controller is deployed, the ingress' nginx configuration is not refreshed, but intead the previous version will keep running. So everything seems fine, until one day the pod restarts, and you're presented with a missing ingress...
Upgrade ingress-nginx Helm chart to 4.11.5
knexxx1337 commentedon Jun 25, 2025
Possible. but If change rules for www-data and create a new rules iptables
tabbysable commentedon Jul 4, 2025
/close
k8s-ci-robot commentedon Jul 4, 2025
@tabbysable: Closing this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
shunsuke-h-opn commentedon Jul 14, 2025
@whereisaaron
Sorry, I have a question about your message.
We are still using v1.8.x.
Is Upgrading to v1.9.7 an one of the resolutions or it's a temporary solution, to avoid that issue completely, need to upgraded the latest one?
whereisaaron commentedon Sep 19, 2025
This is probably way too late @shunsuke-h-op but for the record, you needed to get to v1.11.5. I was suggesting to back-port to a (non-existent) 1.9.7 if easy, to cover users using commercially supported k8s.
shunsuke-h-opn commentedon Sep 19, 2025
@whereisaaron Thank you for answering.
Why I was asking is that our client want to skip to upgrade at some point.
we will proceed to upgrade until latest version.