CVE-2025-1974

CVE-2025-1974 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 99% places it in the 100th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-653.

Key facts

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

Frequently asked questions

What is CVE-2025-1974?
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.)
How severe is CVE-2025-1974?
CVE-2025-1974 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-1974 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 99% (100th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-1974?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-1974 have an EU (EUVD) identifier?
Yes. CVE-2025-1974 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8035.
When was CVE-2025-1974 published?
CVE-2025-1974 was published on 2025-03-25 and last updated on 2026-06-17.

References

Other CWE-653 vulnerabilities

Browse all CWE-653 vulnerabilities →