Advisory

GHSA-4g2f-xcph-2335

Also known as: CVE-2026-24513, GO-2026-4419

Summary

ingress-nginx has Improper Check for Unusual or Exceptional Conditions

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-02-04 00:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

k8s.io/ingress-nginx

Go · All systems

Affected

  • introduced 0, fixed 1.13.7 (semver)

Fixed versions

1.13.7

Fix

k8s.io/ingress-nginx

Go · All systems

Affected

  • introduced 1.14.0, fixed 1.14.3 (semver)

Fixed versions

1.14.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences