CVE-2026-118899

Uncontrolled Resource Consumption
Affects
nginx (ngx_http_request_body.c, ngx_http_v3_request.c); registry.k8s.io/ingress-nginx/controller
in
Ingress NGINX
No items found.
Versions
NGINX Open Source >=1.13.0 <1.30.7, >=1.31.0 <1.31.9; Ingress NGINX Controller builds that compile an affected NGINX, including upstream v1.15.1

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

NGINX Open Source is a web server, reverse proxy and load balancer. Ingress NGINX Controller is an ingress controller for Kubernetes that uses NGINX as a reverse proxy and load balancer. It embeds an NGINX Open Source build and generates NGINX configuration from Ingress objects and annotations, so an NGINX-layer flaw ships inside the controller image rather than being something the cluster operator compiled directly. It is one of the most widely deployed ingress controllers in production Kubernetes clusters, routing external HTTP/HTTPS traffic to Services running inside the cluster.

A denial of service vulnerability (CVE-2026-118899) has been identified in the request body handling of NGINX, which allows remote, unauthenticated attackers to send a crafted TLS 1.3 connection that puts a worker process into an infinite loop while it reads the HTTP request body. The worker then stops accepting new connections and processing existing ones.

Per OWASP: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed.

This issue affects NGINX Open Source versions from 1.13.0 before 1.30.7, and 1.31.x before 1.31.9, and every build that compiles the affected request body code: the upstream Ingress NGINX Controller v1.15.1 and NES for Ingress NGINX v1.15.1-nes-1.15.11 and earlier. Upstream NGINX fixed it in 1.30.7 and 1.31.9. The Kubernetes ingress-nginx project retired in March 2026 at v1.15.1 and will not ship a release that absorbs the fix.

Details

Module Info

  • Product: NGINX Open Source (HTTP request body handling); compiled into the Ingress NGINX Controller image
  • Affected packages: nginx (ngx_http_request_body.c, ngx_http_v3_request.c), registry.k8s.io/ingress-nginx/controller
  • Affected versions:
    • NGINX Open Source: >=1.13.0 <1.30.7, >=1.31.0 <1.31.9
    • Ingress NGINX Controller: builds that compile an affected NGINX, including upstream v1.15.1 and NES for Ingress NGINX v1.15.1-nes-1.15.11 and earlier
  • GitHub repository: https://github.com/nginx/nginx (Ingress NGINX Controller: https://github.com/kubernetes/ingress-nginx)
  • Published packages: https://nginx.org/en/download.html (NGINX Open Source); registry.k8s.io/ingress-nginx/controller and https://kubernetes.github.io/ingress-nginx (Ingress NGINX Controller image and Helm chart)
  • Package manager: Not applicable. NGINX Open Source ships as source releases and OS packages, and Ingress NGINX Controller as a container image with a Helm chart and kubectl manifests.
  • Fixed in:

Vulnerability Info

F5, acting as CNA, scored CVE-2026-118899 at 7.5 (High) on CVSS v3.1 and 8.7 (High) on CVSS v4.0. This High-severity vulnerability is found in the nginx package in multiple versions of NGINX, in the code that reads the client request body.

NGINX reads a request body by calling c->recv() in a loop for as long as the connection's read event is ready (c->read->ready is set). With SSL, c->read->ready can stay set when c->recv() returns NGX_AGAIN, for example when OpenSSL reports SSL_ERROR_WANT_WRITE. The loop did not handle that case, so a crafted TLS 1.3 connection can keep a worker spinning in it forever. While it spins, the worker stops accepting new connections and stops processing the connections it already holds. The HTTP/3 request body reader has the same loop.

The flaw is reachable from any client, without authentication, on an SSL server (listen ... ssl) with TLS 1.3 enabled, at any location that reads the request body, such as a proxied location. TLS 1.3 is enabled by default in ssl_protocols.

In the Ingress NGINX Controller every TLS server reads request bodies through this code, and the default ssl-protocols value is TLSv1.2 TLSv1.3, so the flaw is reachable without authentication on any HTTPS Ingress; the HTTP/3 path is reachable only through configuration snippets.

Mitigation

Ingress NGINX Controller is End-of-Life: the Kubernetes ingress-nginx project retired in March 2026 at v1.15.1 and will not ship a release that absorbs this fix. For more information see here.

Users of the affected components should apply one of the following mitigations:

  • Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline) or later.
  • Move the Ingress NGINX Controller to a maintained build that ships the fixed NGINX.
  • Leverage a commercial support partner like HeroDevs for post-EOL security support.

Credits

  • F5 (finder)
Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
High
ID
CVE-2026-118899
PROJECT Affected
nginx (ngx_http_request_body.c, ngx_http_v3_request.c); registry.k8s.io/ingress-nginx/controller
Versions Affected
NGINX Open Source >=1.13.0 <1.30.7, >=1.31.0 <1.31.9; Ingress NGINX Controller builds that compile an affected NGINX, including upstream v1.15.1
NES Versions Affected
1.15.1-nes-1.15.11 and earlier
Published date
November 19, 2026
≈ Fix date
November 19, 2026
Category
Uncontrolled Resource Consumption
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Ingress NGINX
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.