CVE
CVE-2026-24513
Kubernetes · ingress-nginx
- First Reported
- Feb 20, 2026
- Latest Reported
- Feb 20, 2026
CVE Enrichment
- CVSS
- 3.1 LOW
- EPSS
- 0.35%
- EPSS Percentile
- 28.39%
- CISA KEV
- Not listed
Description
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.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- [email protected]
- Published
- 04-Feb-2026 06:16
- Last Modified
- 17-Jun-2026 17:23
- EPSS Date
- 2026-11-10
- CWE
- CWE-754
CVSS Vector
CVSS:3.1 AV:N /
AC:H /
PR:L /
UI:N /
S:U /
C:L /
I:N /
A:N
CNA Products / Version Status
- Kubernetes · ingress-nginx
Source: CNA · [email protected]
Default status: affected
0 ≤ version < 1.13.7 — affected (semver)
0 ≤ version < 1.14.3 — affected (semver)
repo: https://github.com/kubernetes/ingress-nginx
References
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (1)
- Four new HIGH severity CVEs (CVE-2026-1580, CVE-2026-24512, CVE-2026-24513, CVE-2026-24514) were disclosed on Feb 2, 2026, underscoring the ongoing risk of running unmaintained Ingress NGINX. Kubernetes’ Ingress NGINX Retirement Leaves Deployments Without Patches After March 2026
CVE (4)
MITRE ATT&CK (1)
Vendors (1)
Products (3)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
