CVE-2026-123633
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-123633) has been identified in the HTTP/2 module of NGINX, which allows remote, unauthenticated attackers to trigger a use-after-free in a worker process that is running low on worker_connections. This can crash the worker or corrupt its memory, and F5 notes that attackers can execute code on systems where Address Space Layout Randomization (ASLR) is disabled or can be bypassed.
Per OWASP: Use after free errors occur when a program continues to use a pointer after it has been freed. The use of previously freed memory can have any number of adverse consequences - ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw.
This issue affects NGINX Open Source versions from 1.19.7 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.19.7 <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-123633 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).
When a worker process runs short of worker_connections, NGINX frees slots by closing connections it has registered as reusable. An HTTP/2 connection that held a partial frame read from the client was registered as reusable, and it stayed reusable after a stream was created on it. A worker short on connections could then drain that connection while one of its streams was connecting to an upstream server. NGINX tried to send a GOAWAY frame, the send failed, and the connection was closed and its memory pool freed while the code connecting the stream to the upstream still used it.
Exploitation needs HTTP/2 enabled for client connections, requests proxied to a backend, and a worker close to its worker_connections limit, which a client can bring about by opening connections.
In the Ingress NGINX Controller the flaw is reachable without authentication: the generated configuration enables http2 on for TLS servers, Ingress traffic is proxied to backend Services, and a client can use up worker_connections (the max-worker-connections ConfigMap key) by opening connections.
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
- Albert Ebb Metnir from metnir.com (finder)
- Nir Ohfeld from Wiz Research (finder)
- Xint.io (finder)
- memN0ps from Palo Alto Networks Unit 42 (finder)