Advisory record · GHSA-2pf9-vr92-6h3v

ingress-nginx vulnerable to Allocation of Resources Without Limits or Throttling

CVSS 6.5 MediumEPSS 0.0052 · 44th 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-2pf9-vr92-6h3v · CVE-2026-24514 · GO-2026-4417
Weakness (CWE)
CWE-770
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 (k8s.io/ingress-nginx) versions before 1.13.7 and from 1.14.0 before 1.14.3 are vulnerable. An attacker who can send requests to the validating admission controller can submit large requests that consume memory, potentially getting the controller pod killed or exhausting node memory. Upgrade to version 1.13.7 or 1.14.3.

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
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (kubernetes)
  • CISA KEV Not listed.
  • EPSS 0.0052, the 44th percentile, on 16 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.