CVE-2026-24513: K8s.io/ingress nginx Ingress-nginx Has Improper Check For Vulnerability

LOW
Advisory Identifier: GHSA-4g2f-xcph-2335
CVSS 3.1
CWE-754
Published
Advisory Summary

CVE-2026-24513 is a LOW (CVSS 3.1) ingress-nginx has improper check for vulnerability (CWE-754: Improper Check for Unusual or Exceptional Conditions) affecting K8s.io/ingress nginx libraries in the Go ecosystem. The issue involves ingress-nginx has improper check for unusual or exceptional conditions. Remediation is available by upgrading affected packages to version 1.13.7, 1.14.3.

CVE-2026-24513 at a Glance

CVE Identifier CVE-2026-24513
GHSA Identifier GHSA-4g2f-xcph-2335
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-754: Improper Check for Unusual or Exceptional Conditions
Affected Product K8s.io/ingress nginx
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-24513

To remediate this vulnerability, upgrade all affected K8s.io/ingress nginx dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

k8s.io/ingress-nginx fixed: 1.13.7
Upgrade k8s.io/ingress-nginx to 1.13.7
k8s.io/ingress-nginx fixed: 1.14.3
Upgrade k8s.io/ingress-nginx to 1.14.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for k8s.io/ingress-nginx

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-24513, inspect your project dependencies for K8s.io/ingress nginx:

inspect dependencies for k8s.io/ingress-nginx

Analyze the terminal output to locate any version of K8s.io/ingress nginx in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.13.7), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-754: Improper Check for Unusual or Exceptional Conditions, where the product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. In K8s.io/ingress nginx, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-24513 Affected K8s.io/ingress nginx Versions

2 component(s)
Fixed Versions:
1.13.71.14.3
Product / Package Ecosystem Affected Versions Fixed Version
k8s.io/ingress-nginx
Go
< 1.13.7
1.13.7
k8s.io/ingress-nginx
Go
≥ 1.14.0
< 1.14.3
1.14.3

References

Frequently Asked Questions

What is CVE-2026-24513?
CVE-2026-24513 is a security vulnerability in K8s.io/ingress nginx involving ingress-nginx has Improper Check for Unusual or Exceptional Conditions under CWE-754: Improper Check for Unusual or Exceptional Conditions.
Which K8s.io/ingress nginx versions are affected?
Affected versions include releases prior to 1.13.7, 1.14.3 across affected packages: k8s.io/ingress-nginx.
What version fixes CVE-2026-24513?
Upgrading to 1.13.7, 1.14.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is k8s.io/ingress-nginx affected?
Yes, k8s.io/ingress-nginx is affected in releases prior to 1.13.7, 1.14.3. Upgrade your dependency to 1.13.7, 1.14.3 or later.
What is the CVSS score of CVE-2026-24513?
CVE-2026-24513 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-24513?
CVE-2026-24513 is classified under CWE-754: Improper Check for Unusual or Exceptional Conditions (The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.).
How can I check Go dependencies for CVE-2026-24513?
Run the dependency tree command: 'inspect dependencies for k8s.io/ingress-nginx'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4g2f-xcph-2335",
  "modified" : "2026-02-04T20:05:31Z",
  "published" : "2026-02-04T00:30:29Z",
  "aliases" : [ "CVE-2026-24513" ],
  "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.\n\nIf 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.\n\nNote 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" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "k8s.io/ingress-nginx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.13.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "k8s.io/ingress-nginx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.14.0"
      }, {
        "fixed" : "1.14.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-24513"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kubernetes/kubernetes/issues/136679"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kubernetes/ingress-nginx"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-754" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-04T20:05:31Z",
    "nvd_published_at" : "2026-02-03T23:16:07Z"
  }
}