How severe is CVE-2025-1974?

CVE-2025-1974 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-1974?

Affected package information for CVE-2025-1974 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-1974?

No fixed version has been published for CVE-2025-1974 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2025-1974 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2025-1974, including 2 documented proof-of-concept exploits on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-1974?

CVE-2025-1974 has an EPSS (Exploit Prediction Scoring System) score of 91.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2025-1974?

CVE-2025-1974 is classified as CWE-653 (CWE-653). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2025-1974?

A Nuclei detection template exists for CVE-2025-1974, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-1974 published, and has it been updated?

CVE-2025-1974 was published on March 25, 2025 and was last updated on April 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2025-1974

CRITICAL

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…

Published

Mar 25, 2025

Updated

Apr 15, 2026

Affected

0 pkgs

Patched

None yet

Exploits

7 known

EPSS Exploitation Probability

via FIRST.org ↗

91.9%probability of exploitation in next 30 days

Very High Risk100th percentile+0.79%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52475remotemultiple

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

by Beatriz Fresno Naumova · Feb 4, 2026

Exploit-DB Source

EDB-52338remotemultiple✓ Verified

Ingress-NGINX 4.11.0 - Remote Code Execution (RCE)

by Likhith Appalaneni · Jun 20, 2025

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-1974 in your stack?

O3 detects CVE-2025-1974 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works