BIT-nginx-ingress-controller-2026-24513

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/nginx-ingress-controller/BIT-nginx-ingress-controller-2026-24513.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-nginx-ingress-controller-2026-24513
Withdrawn
2026-05-20T08:00:05Z
Published
2026-02-12T08:45:49Z
Modified
2026-05-20T08:11:53Z
Summary
ingress-nginx auth-url protection bypass
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. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component.

Database specific
{
    "cpes":  [
        "cpe:2.3:a:kubernetes:ingress-nginx:*:*:*:*:*:go:*:*"
    ],
    "severity":  "Low"
}
References

Affected packages

Bitnami / nginx-ingress-controller

Package

Name
nginx-ingress-controller
Purl
pkg:bitnami/nginx-ingress-controller

Severity

  • 3.1 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
1.13.7
Introduced
1.14.0
Fixed
1.14.3

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/nginx-ingress-controller/BIT-nginx-ingress-controller-2026-24513.json"