Read the docs
TI-2026-19756 Aliases CVE-2026-24513GHSA-4g2f-xcph-2335

ingress-nginx auth-url protection bypass

Priority LOW 15CWE-754Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00346 28th percentileScored 2026-11-07
Fix Fixed ingress-nginx (Kubernetes): 1.13.7, 1.14.3k8s.io/ingress-nginx (Go): 1.13.7, 1.14.3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Kubernetesingress-nginxbefore 1.13.7; before 1.14.31.13.7, 1.14.3Patch availableCNA
—k8s.io/ingress-nginx (Go)before 1.13.71.13.7Patch availableGHSA-4g2f-xcph-2335
—k8s.io/ingress-nginx (Go)1.14.0 to before 1.14.31.14.3Patch availableGHSA-4g2f-xcph-2335
  • ingress-nginx VendorKubernetes Affected before 1.13.7; before 1.14.3 Fixed in 1.13.7, 1.14.3 Patch available CNA
  • k8s.io/ingress-nginx (Go) Vendor— Affected before 1.13.7 Fixed in 1.13.7 Patch available GHSA-4g2f-xcph-2335
  • k8s.io/ingress-nginx (Go) Vendor— Affected 1.14.0 to before 1.14.3 Fixed in 1.14.3 Patch available GHSA-4g2f-xcph-2335

Remediation

  • Fix · CNA ingress-nginx (Kubernetes) Fixed in 1.13.7, 1.14.3
  • Fix · GHSA-4g2f-xcph-2335 k8s.io/ingress-nginx (Go) Fixed in 1.13.7 Advisory →
  • Fix · GHSA-4g2f-xcph-2335 k8s.io/ingress-nginx (Go) Fixed in 1.14.3 Advisory →

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Kubernetes ingress-nginx 1.13.7, 1.14.3

    4 records Highest priority Priority MEDIUM 2 MEDIUM, 2 LOW

    Other records, highest priority first

    • TI-2026-19755 ingress-nginx auth-method nginx configuration injectionPriority MEDIUM 41
    • TI-2026-01268 ingress-nginx auth-method nginx configuration injectionPriority MEDIUM 41
    • TI-2026-19757 ingress-nginx Admission Controller denial of servicePriority LOW 29
    Show all 4 records →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-24513
  2. 2026-10-03 Alias added: GHSA-4g2f-xcph-2335

References

Advisory 1

Other 2

  • TI-2025-01719 ingress-nginx admission controller RCE escalation CVSS 3.1CRITICAL 9.8
  • TI-2018-16130 Improper privilege management in Kubernetes CVSS 3.0CRITICAL 9.8
  • TI-2025-00932 ingress-nginx controller - configuration injection via unsanitized mirror annotations CVSS 3.1HIGH 8.8
  • TI-2019-08418 Kubernetes kubelet exposes /debug/pprof info on healthz port CVSS 3.1HIGH 8.2
  • TI-2026-02839 ingress-nginx rewrite-target nginx configuration injection CVSS 3.1HIGH 8.8
  • TI-2025-18233 ingress-nginx controller - configuration injection via unsanitized auth-url annotation CVSS 3.1HIGH 8.8
See all 126 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences