Advisory record · GHSA-4g2f-xcph-2335

ingress-nginx has Improper Check for Unusual or Exceptional Conditions

CVSS 3.1 LowEPSS 0.0035 · 28th percentile

Published by the GitHub Advisory Database at 4 Feb 2026, 00:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
k8s.io/ingress-nginxGo<1.13.7 || >=1.14.0, <1.14.31.13.7, 1.14.3
Identifiers
GHSA-4g2f-xcph-2335 · CVE-2026-24513 · GO-2026-4419
Weakness (CWE)
CWE-754
Published
4 Feb 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Ingress-nginx versions below 1.13.7 and versions from 1.14.0 before 1.14.3 may not enforce the `auth-url` annotation when authentication fails. This requires the controller to be configured with a default custom-errors setting that includes HTTP 401 or 403 and a defective custom-errors backend that ignores the X-Code header, in which case an Ingress protected by `auth-url` could be reached without valid authentication. Upgrade to version 1.13.7 or 1.14.3. The built-in custom-errors backend is not affected.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
3.1 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (kubernetes)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 28th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.