Authentication bypass via ignored X-Code header
Published Feb 3, 2026 · Updated Feb 3, 2026
Authentication bypass in Kubernetes ingress-nginx before 1.13.7 and 1.14.0 through 1.14.2 allows attackers to access protected content. A controller-wide custom-errors backend that ignores the X-Code header mishandles 401 or 403 responses from auth-url and serves the protected Ingress content. Exploitation requires an administrator to configure that defective external backend; the built-in backend and per-Ingress custom errors are unaffected.
Summary
What happened
Authentication bypass in Kubernetes ingress-nginx before 1.13.7 and 1.14.0 through 1.14.2 allows attackers to access protected content. A controller-wide custom-errors backend that ignores the X-Code header mishandles 401 or 403 responses from auth-url and serves the protected Ingress content. Exploitation requires an administrator to configure that defective external backend; the built-in backend and per-Ingress custom errors are unaffected.
The record
- CVE
- CVE-2026-24513
- Published
- Feb 3, 2026
- Updated
- Feb 3, 2026
- Vendor
- Kubernetes
- Product
- ingress-nginx
- Classifications
- CWE-754, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2026CVE publishedPublication date reported by the CVE source.
- Feb 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.13.7
- Affected versionversion=0 <1.14.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo