Skip to content

CVE-2025-1974: ingress-nginx admission controller RCE escalation #131009

Closed

Description

@tabbysable

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

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

  1. added
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Mar 23, 2025
  2. tabbysable commented on Mar 23, 2025

    @tabbysable
    MemberAuthor

    /triage accepted

  3. added
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    and removed
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Mar 23, 2025
  4. thisisharrsh commented on Mar 24, 2025

    @thisisharrsh

    Hi @tabbysable, Please add the issue description for better understanding of the issue.
    /triage needs-information

  5. changed the title [-]Placeholder Issue[/-] [+]CVE-2025-1974: ingress-nginx admission controller RCE escalation[/+] on Mar 24, 2025
  6. tabbysable commented on Mar 24, 2025

    @tabbysable
    MemberAuthor

    /area security
    /kind bug
    /committee security-response
    /label official-cve-feed
    /sig network

  7. added
    kind/bugCategorizes issue or PR as related to a bug.
    committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.
    sig/networkCategorizes an issue or PR as relevant to SIG Network.
    official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)
    and removed
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Mar 24, 2025
  8. 45 remaining items

  9. Mr-P-D commented on Mar 27, 2025

    @Mr-P-D

    Based on the official comments from the Kubernetes Blog, PODs can only be accessed by the people/user in the same VPC/corporate network.

    Image

    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/

  10. tuminoid commented on Mar 27, 2025

    @tuminoid

    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.

    From the wiz.io blog:

    Image

    Some folks publicly expose the admission controller, which warrants Network I believe 🤷

  11. suhettfilipe commented on Mar 28, 2025

    @suhettfilipe

    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

  12. added a commit that references this issue on Mar 31, 2025
  13. ntavares commented on Apr 1, 2025

    @ntavares

    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 help I 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...

  14. knexxx1337 commented on Jun 25, 2025

    @knexxx1337

    I'm researching ways to mitigate the attack surface of this CVE, and I currently have a question regarding the attack payload injection via the ingress controller.

    Specifically, if we prevent reading file descriptors (like /proc/xx/fd/xxx) within the container using the www-data user, would this effectively reduce the attack surface associated with this vulnerability?

    Or are there alternative methods to inject payloads without relying on file descriptor access?

    Possible. but If change rules for www-data and create a new rules iptables

  15. tabbysable commented on Jul 4, 2025

    @tabbysable
    MemberAuthor

    /close

  16. k8s-ci-robot commented on Jul 4, 2025

    @k8s-ci-robot
    Contributor

    @tabbysable: Closing this issue.

    Details

    In response to this:

    /close

    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.

  17. shunsuke-h-opn commented on Jul 14, 2025

    @shunsuke-h-opn

    Hi, thank you for these quick releases! Right now AWS still provides extended commercial support for k8s v1.25, which can only deploy nginx-ingress up to v1.9.6, so there would likely be value for quite a few users in a patched build v1.9.7.

    Upgrading the entire cluster to v1.26 in order to access v1.11.5 would be another option, but that's a much bigger task. So a patched v1.9.7 would enable faster resolution of these issues.

    @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?

  18. whereisaaron commented on Sep 19, 2025

    @whereisaaron

    @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?

    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.

  19. shunsuke-h-opn commented on Sep 19, 2025

    @shunsuke-h-opn

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/securitycommittee/security-responseDenotes an issue or PR intended to be handled by the product security committee.kind/bugCategorizes issue or PR as related to a bug.official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)sig/networkCategorizes an issue or PR as relevant to SIG Network.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions