CVE-2025-1974: ingress-nginx admission controller RCE escalation
Noroxi assessment
Priority: This week (action score 69/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 99.4% (FIRST EPSS); higher than 99.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: k8s.io/ingress-nginx (Go) 1.12.1, 1.11.5; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250327T184518-1.1; rke2 (openSUSE:Tumbleweed) 1.32.3+rke2r1-1.1.
Don’t wait for the next maintenance window. Upgrade to k8s.io/ingress-nginx (Go) 1.12.1, 1.11.5; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250327T184518-1.1; rke2 (openSUSE:Tumbleweed) 1.32.3+rke2r1-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Mar 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 99.4% · 99th percentile
- CWE
- CWE-653
Report tools
Action score
69
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 30 / 30 · 99.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · kubernetes
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.
kubernetes ingress-nginx
- 1.12.0affected
- up to and including 1.11.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | k8s.io/ingress-nginx | from 0 | — |
| Go | k8s.io/ingress-nginx | from 1.12.0-beta.0 · before 1.12.1 | 1.12.1 |
| Go | k8s.io/ingress-nginx | before 1.11.5 | 1.11.5 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250327T184518-1.1 | 0.0.20250327T184518-1.1 |
| openSUSE:Tumbleweed | rke2 | before 1.32.3+rke2r1-1.1 | 1.32.3+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.29 | before 1.29.15+rke2r1-1.1 | 1.29.15+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.30 | before 1.30.11+rke2r1-1.1 | 1.30.11+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.31 | before 1.31.7+rke2r1-1.1 | 1.31.7+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.32 | before 1.32.4+rke2r1-1.1 | 1.32.4+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.33 | before 1.33.5+rke2r1-1.1 | 1.33.5+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.34 | before 1.34.3+rke2r1-1.1 | 1.34.3+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.35 | before 1.35.4+rke2r1-1.1 | 1.35.4+rke2r1-1.1 |
| openSUSE:Tumbleweed | rke2-1.36 | before 1.36.4+rke2r1-1.1 | 1.36.4+rke2r1-1.1 |
Same product
kubernetes: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-1098ingress-nginx controller - configuration injection via unsanitized mirror annotations61This week
- CVE-2023-5044Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation51Plan
- CVE-2025-24514ingress-nginx controller - configuration injection via unsanitized auth-url annotation46Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-7646Aug 16, 2024 · A security issue was discovered in ingress-nginx where an actor with permission to create Ingress objects (in the `networking.k8s.io` or…43Plan
- ← EarlierCVE-2025-1097Mar 24, 2025 · ingress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation46Plan
- Later →CVE-2025-24513Mar 24, 2025 · ingress-nginx controller - auth secret file path traversal vulnerability20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:k8s.io/ingress-nginx | 1.11.5 | Package registry (OSV) |
| Go:k8s.io/ingress-nginx | 1.12.1 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250327T184518-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2 | 1.32.3+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.29 | 1.29.15+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.30 | 1.30.11+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.31 | 1.31.7+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.32 | 1.32.4+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.33 | 1.33.5+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.34 | 1.34.3+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.35 | 1.35.4+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:rke2-1.36 | 1.36.4+rke2r1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×2
- Nuclei detection template ×2
- Proof-of-concept repository on GitHub ×25
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 25 repositories | 2025-03-24 → 2026-11-01 |
| Exploit-DB entry | remote | 2025-06-20 |
| Exploit-DB entry | remote | 2026-02-04 |
| Nuclei detection template | Nuclei template CVE-2025-1974-k8s | — |
| Nuclei detection template | Nuclei template CVE-2025-1974 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-1 d
- Published
- TodayNov 16, 2026+601 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sagi TzadikWiz.iofinder
- Nir Ohfeldfinder
- Ronen Shustinfinder
- Hillai Ben Sassonfinder
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-653 · Improper Isolation or CompartmentalizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.