PT-2026-6359 · Go · K8S.Io/Ingress-Nginx

Published 2026-02-04 · Updated 2026-02-04

OSV

CVSS v3.1

3.1

Low

Base vector

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

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. Triggering this issue requires an administrator to specifically configure ingress-nginx with a broken external component.

Fix

Improper Check for Exceptional Conditions

Weakness Enumeration

CWE-754

Related Identifiers

GHSA-4G2F-XCPH-2335

Affected Products

K8S.Io/Ingress-Nginx

References · 4

• https://osv.dev/vulnerability/GHSA-4g2f-xcph-2335 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2026-24513 · Security Note
• https://github.com/kubernetes/kubernetes/issues/136679 · Note
• https://github.com/kubernetes/ingress-nginx · Note