# k8s.io/ingress-nginx (Go) vulnerabilities 17 known vulnerabilities (1 critical, 11 high, 4 medium, 1 low), with the versions each affects and the releases that fix them. ## At a glance - Latest release: v1.0.0-alpha.1 (Jun 23, 2021): affected by 15 advisories - Newest unaffected release: Every release is affected by at least one advisory - Releases: 1 since v1.0.0-alpha.1 (Jun 23, 2021) - Registry: https://pkg.go.dev/k8s.io/ingress-nginx - Releases read: Nov 8, 2026 ## Version timeline Affected versions per advisory, in version order: - CVE-2026-4342: no published release is affected - CVE-2026-24514: v1.0.0-alpha.1 (through the newest release) - CVE-2026-24513: v1.0.0-alpha.1 (through the newest release) - CVE-2026-24512: v1.0.0-alpha.1 (through the newest release) - CVE-2026-1580: v1.0.0-alpha.1 (through the newest release) - CVE-2025-24514: v1.0.0-alpha.1 (through the newest release) - CVE-2025-24513: v1.0.0-alpha.1 (through the newest release) - CVE-2025-1098: v1.0.0-alpha.1 (through the newest release) - CVE-2025-1097: v1.0.0-alpha.1 (through the newest release) - CVE-2025-1974: v1.0.0-alpha.1 (through the newest release) - CVE-2023-5044: v1.0.0-alpha.1 (through the newest release) - CVE-2023-5043: v1.0.0-alpha.1 (through the newest release) - CVE-2022-4886: v1.0.0-alpha.1 (through the newest release) - CVE-2021-25748: v1.0.0-alpha.1 (through the newest release) - CVE-2021-25745: v1.0.0-alpha.1 (through the newest release) - CVE-2020-8553: no published release is affected - CVE-2018-1002104: v1.0.0-alpha.1 (through the newest release) ## Advisories (17) ### [CVE-2026-4342](https://cve.now/CVE-2026-4342): ingress-nginx comment-based nginx configuration injection - Severity: High 8.8 - Published: Mar 19, 2026 - Affected: fixed in 0.0.0-20260319175635-5183b7d86137. - No fix released. The advisory names 0.0.0-20260319175635-5183b7d86137 as the fix, which the registry doesn't have yet. ### [CVE-2026-24514](https://cve.now/CVE-2026-24514): ingress-nginx Admission Controller denial of service - Severity: Medium 6.5 - Published: Feb 3, 2026 - Affected: fixed in 1.13.7; from 1.14.0, fixed in 1.14.3; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2026-24513](https://cve.now/CVE-2026-24513): ingress-nginx auth-url protection bypass - Severity: Low 3.1 - Published: Feb 3, 2026 - Affected: fixed in 1.13.7; from 1.14.0, fixed in 1.14.3; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2026-24512](https://cve.now/CVE-2026-24512): ingress-nginx auth-method nginx configuration injection - Severity: High 8.8 - Published: Feb 3, 2026 - Affected: fixed in 1.13.7; from 1.14.0, fixed in 1.14.3; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2026-1580](https://cve.now/CVE-2026-1580): ingress-nginx auth-method nginx configuration injection - Severity: High 8.8 - Published: Feb 3, 2026 - Affected: all versions; fixed in 1.13.7; from 1.14.0, fixed in 1.14.3. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2025-24514](https://cve.now/CVE-2025-24514): ingress-nginx controller - configuration injection via unsanitized auth-url annotation - Severity: High 8.8 - Published: Mar 24, 2025 - Affected: all versions; fixed in 1.11.5; from 1.12.0-beta.0, fixed in 1.12.1. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2025-24513](https://cve.now/CVE-2025-24513): ingress-nginx controller - auth secret file path traversal vulnerability - Severity: Medium 4.8 - Published: Mar 24, 2025 - Affected: fixed in 1.11.5; from 1.12.0-beta.0, fixed in 1.12.1; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2025-1098](https://cve.now/CVE-2025-1098): ingress-nginx controller - configuration injection via unsanitized mirror annotations - Severity: High 8.8 - Published: Mar 24, 2025 - Affected: fixed in 1.11.5; from 1.12.0-beta.0, fixed in 1.12.1; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2025-1097](https://cve.now/CVE-2025-1097): ingress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation - Severity: High 8.8 - Published: Mar 24, 2025 - Affected: fixed in 1.11.5; from 1.12.0-beta.0, fixed in 1.12.1; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2025-1974](https://cve.now/CVE-2025-1974): ingress-nginx admission controller RCE escalation - Severity: Critical 9.8 - Published: Mar 24, 2025 - Affected: fixed in 1.11.5; from 1.12.0-beta.0, fixed in 1.12.1; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2023-5044](https://cve.now/CVE-2023-5044): Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation - Severity: High 7.6 - Published: Oct 25, 2023 - Affected: fixed in 1.9.0; all versions. - No fix released. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2023-5043](https://cve.now/CVE-2023-5043): Ingress nginx annotation injection causes arbitrary command execution - Severity: High 7.6 - Published: Oct 25, 2023 - Affected: fixed in 1.9.0. - No fix released. The advisory names 1.9.0 as the fix, which the registry doesn't have yet. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2022-4886](https://cve.now/CVE-2022-4886): Ingress-nginx \`path\` sanitization can be bypassed with \`log\_format\` directive - Severity: High 8.8 - Published: Oct 25, 2023 - Affected: fixed in 1.8.0. - No fix released. The advisory names 1.8.0 as the fix, which the registry doesn't have yet. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2021-25748](https://cve.now/CVE-2021-25748): Ingress-nginx \`path\` sanitization can be bypassed with newline character - Severity: High 7.6 - Published: May 24, 2023 - Affected: fixed in 1.2.1. - No fix released. The advisory names 1.2.1 as the fix, which the registry doesn't have yet. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2021-25745](https://cve.now/CVE-2021-25745): Ingress-nginx path can be pointed to service account token file - Severity: High 7.6 - Published: May 6, 2022 - Affected: fixed in 1.2.0. - No fix released. The advisory names 1.2.0 as the fix, which the registry doesn't have yet. The latest release, v1.0.0-alpha.1, is still affected. ### [CVE-2020-8553](https://cve.now/CVE-2020-8553): Kubernetes ingress-nginx Compromise of auth via subset/superset namespace names - Severity: Medium 5.9 - Published: Jul 29, 2020 - Affected: fixed in 0.28.0. - No fix released. The advisory names 0.28.0 as the fix, which the registry doesn't have yet. ### [CVE-2018-1002104](https://cve.now/CVE-2018-1002104): Versions \< 1.5 of the Kubernetes ingress default backend, which handles invalid ingress traffic, exposed prometheus metrics publicly. - Severity: Medium 5.3 - Published: Jan 14, 2020 - Affected: fixed in 1.5. - No fix released. The advisory names 1.5 as the fix, which the registry doesn't have yet. The latest release, v1.0.0-alpha.1, is still affected. --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/packages/go/k8s.io/ingress-nginx Site guide for agents: https://cve.now/llms.txt Uses NVD data; not endorsed by NVD.