Kubernetes · Kubernetes · published 2026-02-03
CVE-2026-24513ingress-nginx auth-url protection bypass
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-24513 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 28% of all CVEs. This Kubernetes vulnerability: CVSS 3.1 (v3.1). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
OrchestrationKubernetes
Kubernetes security fixes: 4 CVEs
Why: Vendor security release for server software (most severe: CVE-2026-1580).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (29th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.1 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Kubernetes ingress-nginx
0to before1.13.7(affected)0to before1.14.3(affected)
Description (from the CVE record)#
A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration. If the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails. Note that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component.
Quoted from the CVE Program record.