Threadlinqs IntelligenceStart free

VulnerabilityCVE-2025-1974Published 2025-03-24

CVE-2025-1974 — kubernetes ingress-nginx

criticalPublic exploit11 PoC reposNuclei template

As of 2026-02-26, CVE-2025-1974 is a CRITICAL-severity vulnerability in kubernetes ingress-nginx, CVSS v3.1 9.8, EPSS 99.3% (99.9th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2025-1974, most recently “Evooo1Bot: Multi-Functional Mirai-Based Linux Botnet Exploiting 18 Known CVEs in Internet-Facing Devices”.

CVSS v3.1
9.8/10Critical
EPSS
99.3%Higher than 99.9% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
10/10Threadlinqs triage score
Published
Updated 2026-02-26
CVSS v3.1 9.8 (CRITICAL) · EPSS 99.3% (higher than 99.9% of all scored CVEs) · Priority 10/10 · Published 2025-03-24

Last updated:

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

The record classifies CVE-2025-1974 under weakness class CWE-653. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 565 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
99.3% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
10/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2025-03-24, last modified 2026-02-26

Is CVE-2025-1974 being exploited?

Weaponised exploit code for CVE-2025-1974 is publicly available. 11 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2025/CVE-2025-1974.yaml). It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.

Affected products and versions

  • kubernetes: ingress-nginx

Affected software packages:

  • go:k8s.io/ingress-nginx — patched in 1.11.5
  • go:k8s.io/ingress-nginx — patched in 1.12.1

How to fix CVE-2025-1974

Fixed versions are recorded for 2 packages: go:k8s.io/ingress-nginx 1.11.5, go:k8s.io/ingress-nginx 1.12.1. No vendor patch reference has been recorded for CVE-2025-1974 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2025-1974

1 tracked threat in the Threadlinqs corpus references CVE-2025-1974, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories, ProjectDiscovery Nuclei. Last verified by Threadlinqs on .

Other references