CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HKnown as IngressNightmare
Critical (9.8) in kubernetes ingress-nginx. EPSS 99.4% estimated probability of exploitation activity in the next 30 days. Fixed in k8s.io/ingress-nginx 1.11.5, 1.12.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hk8s.io/ingress-nginx (Go): fixed in 1.11.5, 1.12.1Explain CVE-2025-1974 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-1974?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-1974?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-1974 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| kubernetes ingress-nginx | through 1.11.4 |
| kubernetes ingress-nginx | 1.12.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-mgvx-rpfc-9mpv | Go | k8s.io/ingress-nginx | <1.11.5 | 1.11.5 |
| GHSA-mgvx-rpfc-9mpv | Go | k8s.io/ingress-nginx | >=1.12.0-beta.0 <1.12.1 | 1.12.1 |
| GO-2025-3567 | Go | k8s.io/ingress-nginx | all versions | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20250327T184518-1.1 | openSUSE-SU-2025:14937-1 |
| openSUSE | Tumbleweed | rke2 | 1.32.3+rke2r1-1.1 | openSUSE-SU-2025:14941-1 |
| openSUSE | Tumbleweed | rke2-1.29 | 1.29.15+rke2r1-1.1 | openSUSE-SU-2025:14942-1 |
| openSUSE | Tumbleweed | rke2-1.30 | 1.30.11+rke2r1-1.1 | openSUSE-SU-2025:14943-1 |
| openSUSE | Tumbleweed | rke2-1.31 | 1.31.7+rke2r1-1.1 | openSUSE-SU-2025:14944-1 |
| openSUSE | Tumbleweed | rke2-1.32 | 1.32.4+rke2r1-1.1 | openSUSE-SU-2025:15083-1 |
| openSUSE | Tumbleweed | rke2-1.33 | 1.33.5+rke2r1-1.1 | openSUSE-SU-2025:15569-1 |
| openSUSE | Tumbleweed | rke2-1.34 | 1.34.3+rke2r1-1.1 | openSUSE-SU-2026:10050-1 |
| openSUSE | Tumbleweed | rke2-1.35 | 1.35.4+rke2r1-1.1 | openSUSE-SU-2026:10799-1 |
| openSUSE | Tumbleweed | rke2-1.36 | 1.36.4+rke2r1-1.1 | openSUSE-SU-2026:11842-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Red Hat rates this Important.
Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product.
Ingress-NGINX is not the default ingress controller shipped with Red Hat OpenShift. Instead, Red Hat OpenShift ships with and supports its own ingress controller based on HAProxy, known as the OpenShift Router. This controller is fully integrated with OpenShift's networking and security models and is managed by the Ingress Operator.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-1974.
| Advisory | Title | Published | Sectors | Affected | Fixed |
|---|---|---|---|---|---|
| ICSA-25-100-05 | Siemens Insights Hub Private Cloud | 2025-04-08 | Critical Manufacturing | Insights Hub Private Cloud | none listed |
From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.