ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-1974

kubernetes ingress-nginx Improper Isolation or Compartmentalization

Published Mar 23, 2025 · catalog updated Mar 25, 2025 · Kubernetes Kubernetes

Patch now

CVE-2025-1974 is in the CISA known-exploited catalog. Confirm Kubernetes Kubernetes against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
Severity
Unknown—
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
99.38%
Remediation
Remediation guidance
Affected products
vendor kubernetes ingress-nginx

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.) Initial-access exploit intelligence.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor kubernetes ingress-nginxversion unspecified

How to fix CVE-2025-1974

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-1974 is in the CISA known-exploited catalog. Confirm Kubernetes Kubernetes against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Affected version ranges are not on this record. Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

What should an analyst verify?

No weakness class is stored. EPSS 99.38%. The CISA KEV listing is the exploitation evidence. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Kubernetes securityNginx security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 23, 2025 · Kubernetes Security

    Detected

    ingress-nginx admission controller RCE escalation

  2. Mar 25, 2025 · CISA KEV

    Known exploited

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

  3. Mar 25, 2025 · VulnCheck KEV

    Updated

    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.) Initial-access e

Sources

  • CVE.orgVulnerability recordCVE-2025-1974

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-1974

    30-day exploitation probability 99.4%

    first.org
  • Kubernetes SecurityVendor advisoryCVE-2025-1974

    ingress-nginx admission controller RCE escalation

    github.com
  • VulnCheck KEVConfirmed exploitationCVE-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 c

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.