Skip to content
OpenAdvisories
Low · 3.1 CVE-2026-24513 EUVD-2026-5383GHSA-4g2f-xcph-2335GO-2026-4419

ingress-nginx auth-url protection bypass

Published Feb 3, 2026 · Updated Feb 18, 2026 · Assigned by kubernetes

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.

Affected products

VendorProductAffectedFixed
Kubernetes ingress-nginx < 1.13.7, < 1.14.3 1.13.7

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Leap 16.0 govulncheck-vulndb 0.0.20260723T184607-160000.1.1 openSUSE-SU-2026:21483-1
openSUSE Leap 15.6 govulncheck-vulndb 0.0.20260205T172317-150000.1.146.1 SUSE-SU-2026:0403-1

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling ingress-nginx-controller-1.12 No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
Go k8s.io/ingress-nginx < 1.13.7 1.13.7 GHSA-4g2f-xcph-2335
Go k8s.io/ingress-nginx >= 1.14.0, < 1.14.3 1.14.3 GHSA-4g2f-xcph-2335
Go k8s.io/ingress-nginx all versions — GO-2026-4419

Advisories 3

References