CVE-2026-123007
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 remote code execution vulnerability (CVE-2026-123007) has been identified in the HTTP/2 module of NGINX, which allows remote, unauthenticated attackers to push the HTTP/2 flow control window past its limit and cause a heap buffer overflow in a worker process. This usually crashes the worker, and F5 notes that attackers can execute code on systems where Address Space Layout Randomization (ASLR) is disabled or can be bypassed.
Per OWASP: A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold or when a program attempts to put data in a memory area past a buffer. In this case, a buffer is a sequential section of memory allocated to contain anything from a character string to an array of integers. Writing outside the bounds of a block of allocated memory can corrupt data, crash the program, or cause the execution of malicious code.
This issue affects NGINX Open Source versions from 1.9.5 before 1.30.7, and 1.31.x before 1.31.9, and every build that compiles the affected HTTP/2 module: 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/2 module); compiled into the Ingress NGINX Controller image
- Affected packages:
nginx(ngx_http_v2_module),registry.k8s.io/ingress-nginx/controller - Affected versions:
- NGINX Open Source: >=1.9.5 <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:
- OSS NGINX 1.30.7, 1.31.9
- NES for Ingress NGINX v1.15.1-nes-1.15.12
Vulnerability Info
F5, acting as CNA, scored CVE-2026-123007 at 8.1 (High) on CVSS v3.1 and 9.2 (Critical) on CVSS v4.0. This High-severity vulnerability is found in the nginx package in multiple versions of NGINX, in the HTTP/2 module (ngx_http_v2_module).
HTTP/2 flow control limits how much response data NGINX may send, on each stream and on the connection as a whole. When a stream was terminated, NGINX refunded the stream's queued but unsent payload to the connection's send window. If the client had raised that window with a WINDOW_UPDATE frame after the stream's frames were queued, the refund pushed the window past NGX_HTTP_V2_MAX_WINDOW, the largest window the protocol allows. ngx_http_v2_send_chain() relies on the window to bound the size of the buffers it sends, so the oversized window broke that bound and led to a heap buffer overflow, usually followed by a segmentation fault in the worker process. The client controls every step of the sequence: it sends the WINDOW_UPDATE frames and resets the streams.
In the Ingress NGINX Controller the flaw is reachable without authentication: the generated configuration enables http2 on for TLS servers, and the bug is driven entirely by client WINDOW_UPDATE frames and stream resets.
When successfully exploited, this vulnerability can lead to:
- Denial of service through worker process crashes, which for an ingress controller drops or degrades request handling for every Service behind it
- Corruption of worker process memory
- Remote code execution in the NGINX worker process on systems where ASLR is disabled or can be bypassed
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
- Stephen Fewer from Rapid7 (finder)
- Tomer Schwartz from Wiz Research (finder)
- Xint.io (finder)
- Ikotas Labs, Inc. (finder)