CVE-2025-1974

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 91% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 99%
CISA-KEV: Not listedEPSS: 99%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.9%
KEV
Not listed

Published

March 25, 2025

Last Modified

April 15, 2026

Advisory Details (2)

Auto-updated May 2, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE - Multiple remote Exploit

https://www.exploit-db.com/exploits/52475
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20250328-0008/

Vendor Advisories for CVE-2025-1974(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
k8s.io/ingress-nginx———

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:02 UTCEPSS rescore
  2. 2026-07-16 17:02 UTCEPSS rescore
  3. 2026-07-10 16:23 UTCOSV refresh
  4. 2026-07-07 13:45 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-24 14:04 UTCEPSS rescore
  8. 2026-06-24 14:04 UTCEPSS rescore
  9. 2026-06-15 17:48 UTCEPSS rescore
  10. 2026-06-12 23:11 UTCEPSS rescore
  11. 2026-06-10 22:18 UTCEPSS rescore
  12. 2026-06-08 14:16 UTCEPSS rescore
  13. 2026-06-08 14:16 UTCEPSS rescore
  14. 2026-06-07 15:24 UTCEPSS rescore
  15. 2026-06-06 13:47 UTCEPSS rescore
  16. 2026-06-06 13:47 UTCEPSS rescore
  17. 2026-06-05 22:46 UTCEPSS rescore
  18. 2026-06-05 22:46 UTCEPSS rescore
  19. 2026-06-05 06:10 UTCEPSS rescore
  20. 2026-06-05 06:10 UTCEPSS rescore
  21. 2026-05-31 00:16 UTCEPSS rescore
  22. 2026-05-31 00:16 UTCEPSS rescore
  23. 2026-05-28 13:44 UTCEPSS rescore
  24. 2026-05-28 13:44 UTCEPSS rescore
  25. 2026-05-28 13:44 UTCEPSS rescore
Show 18 more
  1. 2026-05-28 13:44 UTCEPSS rescore
  2. 2026-05-26 13:43 UTCEPSS rescore
  3. 2026-05-26 13:43 UTCEPSS rescore
  4. 2026-05-26 13:43 UTCEPSS rescore
  5. 2026-05-26 13:43 UTCEPSS rescore
  6. 2026-05-24 16:56 UTCEPSS rescore
  7. 2026-05-23 15:20 UTCEPSS rescore
  8. 2026-05-22 21:16 UTCEPSS rescore
  9. 2026-05-22 21:16 UTCEPSS rescore
  10. 2026-05-22 21:16 UTCEPSS rescore
  11. 2026-05-21 16:22 UTCEG score recompute
  12. 2026-05-21 16:22 UTCVendor advisory
  13. 2026-05-20 11:21 UTCEPSS rescore
  14. 2026-05-20 11:21 UTCEPSS rescore
  15. 2026-05-20 11:21 UTCEPSS rescore
  16. 2026-05-20 11:21 UTCEPSS rescore
  17. 2026-05-20 11:21 UTCEPSS rescore
  18. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(8 references)

Working exploit code is in the public domain (5 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52475
    First seen Feb 4, 2026

    Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE

    Open source ↗
  • Exploit-DBEDB-52338✓ verified
    First seen Jun 20, 2025

    Ingress-NGINX 4.11.0 - Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoCzwxxb/CVE-2025-1974
    First seen Mar 26, 2025

    Poc for Ingress RCE

    Open source ↗
  • GitHub PoCEsonhugh/ingressNightmare-CVE-2025-1974-exps
    First seen Mar 26, 2025

    IngressNightmare POC. world first non-blind remote execution exploitation with multi-advanced exploitation methods. allow on disk exploitation. CVE-2025-24514 - auth-url injection, CVE-2025-1097 - auth-tls-match-cn injection, CVE-2025-1098 – mirror UID injection -- all available.

    Open source ↗
  • GitHub PoChi-unc1e/CVE-2025-1974-poc
    First seen Mar 26, 2025

    PoC of CVE-2025-1974, modified from the world-first PoC~

    Open source ↗
  • GitHub PoCyoshino-s/CVE-2025-1974
    First seen Mar 25, 2025
    Open source ↗
  • GitHub PoCsandumjacob/IngressNightmare-POCs
    First seen Mar 24, 2025

    CVE-2025-1974

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-1974.yaml
    First seen Jan 1, 2025

    Ingress-Nginx Controller - Remote Code Execution

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-1974?
CVE-2025-1974 is a critical vulnerability published on March 25, 2025. 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…
When was CVE-2025-1974 disclosed?
CVE-2025-1974 was first published in the National Vulnerability Database on March 25, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-1974 actively exploited?
CVE-2025-1974 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-1974?
CVE-2025-1974 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-1974?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-1974, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-1974

Explore →

Is Your Infrastructure Affected by CVE-2025-1974?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs