# CVE-2025-1974 — kubernetes ingress-nginx

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

**Last updated:** 2026-02-26

## 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](https://cwe.mitre.org/data/definitions/653.html). 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.

- [Esonhugh/ingressNightmare-CVE-2025-1974-exps](https://github.com/Esonhugh/ingressNightmare-CVE-2025-1974-exps) (github)
- [sandumjacob/IngressNightmare-POCs](https://github.com/sandumjacob/IngressNightmare-POCs) (github)
- [yoshino-s/CVE-2025-1974](https://github.com/yoshino-s/CVE-2025-1974) (github)
- [zwxxb/CVE-2025-1974](https://github.com/zwxxb/CVE-2025-1974) (github)
- [hi-unc1e/CVE-2025-1974-poc](https://github.com/hi-unc1e/CVE-2025-1974-poc) (github)
- [1w4y/IngressNightmare-RCE-POC](https://github.com/1w4y/IngressNightmare-RCE-POC) (github)
- [rjhaikal/POC-IngressNightmare-CVE-2025-1974](https://github.com/rjhaikal/POC-IngressNightmare-CVE-2025-1974) (github)
- [Rubby2001/CVE-2025-1974-go](https://github.com/Rubby2001/CVE-2025-1974-go) (github)

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

- [Evooo1Bot: Multi-Functional Mirai-Based Linux Botnet Exploiting 18 Known CVEs in Internet-Facing Devices](https://intel.threadlinqs.com/threat/TL-2026-3062) — HIGH · 2026-10-09

## Sources

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

**Other references**

- [https](https://https//github.com/kubernetes/kubernetes/issues/131009)

Canonical: https://intel.threadlinqs.com/cve/CVE-2025-1974
Full detection coverage and IOCs for threats exploiting CVE-2025-1974 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp