CVE-2025-1974 | ingress-nginx admission controller RCE escalation

Exp

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

Published: 2025-03-24 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-1974 is rated High Exploit Risk (88.9/100): CVSS Critical severity, with high exploitation likelihood (EPSS 99.10%, 100th percentile). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-1974

EDB-ID Source Kind Published Link
52475 exploit_db edb 2026-02-04 Exploit-DB ↗
52338 exploit_db edb 2025-06-20 Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-1974

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-25 99.35% 99.10% -0.25%
2 2026-06-15 91.92% 99.35% +7.43%
3 2026-06-08 — 91.92% —

Full EPSS history (56 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-1974

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2025-1974

GitHub Security Advisory for CVE-2025-1974

GHSA-mgvx-rpfc-9mpv · Severity: critical · Ecosystem: go — ingress-nginx admission controller RCE escalation

OS Trackers for CVE-2025-1974

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2025-1974

Affected software / configurations for CVE-2025-1974

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-1974

cvelogic Threat Intelligence