CVE-2026-24514: GO-2026-4417 - ingress-nginx vulnerable to Allocation of Resources Without Limits or Throttling in k8s.io/ingress-nginx

CVE-2026-24514 · Severity: low · CVSS 3.1 · Published 2026-02-05

ingress-nginx vulnerable to Allocation of Resources Without Limits or Throttling in k8s.io/ingress-nginx

Technologies: k8s.io/ingress-nginx (Go). Vendors: Go.

Quick answers

Is CVE-2026-24514 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-24514 being exploited in the wild.
How severe is CVE-2026-24514?
Low severity, with a CVSS score of 3.1, published 5 February 2026.
Which products and versions are affected?
k8s.io/ingress-nginx (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.13.7.
Is there a fix for CVE-2026-24514?
Yes. k8s.io/ingress-nginx (Go): upgrade to 1.13.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-24514?
Check whether you run k8s.io/ingress-nginx (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • k8s.io/ingress-nginx (Go): upgrade to 1.13.7 or later
    go get k8s.io/ingress-nginx@v1.13.7

Affected products

  • k8s.io/ingress-nginx (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.13.7

Identifiers

  • CVE-2026-24514
  • GHSA-2pf9-vr92-6h3v
  • GO-2026-4417

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.