CVE-2025-1974

ingress-nginx admission controller RCE escalation

Description

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

Remediation

Workaround:

  • Before applying the patch, this issue can be mitigated by disabling the Validating Admission Controller functionality of ingress-nginx.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 87.03% Top 5%
Affected: kubernetes ingress-nginx
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-1974?
CVE-2025-1974 has been scored as a critical severity vulnerability.
How to fix CVE-2025-1974?
As a workaround for remediating CVE-2025-1974: Before applying the patch, this issue can be mitigated by disabling the Validating Admission Controller functionality of ingress-nginx.
Is CVE-2025-1974 being actively exploited in the wild?
It is possible that CVE-2025-1974 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~87% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-1974?
CVE-2025-1974 affects kubernetes ingress-nginx.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.