CVE-2026-123634
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-123634) has been identified in the resolver of NGINX, which allows remote attackers to trigger a use-after-free in a worker process with a crafted HTTP request when a proxied server name is resolved at request time and a subrequest resolves the same name. 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 0.6.18 before 1.30.7, and 1.31.x before 1.31.9, and every build that compiles the affected resolver: 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 (resolver); compiled into the Ingress NGINX Controller image
- Affected packages:
nginx(resolver,ngx_resolver.c),registry.k8s.io/ingress-nginx/controller - Affected versions:
- NGINX Open Source: >=0.6.18 <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-123634 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 resolver (ngx_resolver.c).
The NGINX resolver lets several resolve contexts wait on the same name or address, and calls each context's handler when the answer arrives. When one resolve handler finalized another, non-current resolve of the same name or address, the finalized resolve could still be reported after its memory was released. One way to reach this is a request that is terminated from the upstream resolve handler while a subrequest resolves the same name.
F5 describes the conditions: NGINX is configured as a proxy, the proxied server name includes variables (so it is resolved at request time through the resolver directive), and a Server Side Includes (SSI) include or a mirror directive sends a subrequest to a location that resolves the same server name.
In the Ingress NGINX Controller the flaw is reachable on Ingresses that use external authentication: the generated configuration sets resolver in the http block, and the auth-url annotation renders set $target <url>; proxy_pass $target; in the auth_request location, so a hostname in auth-url is resolved at request time inside a subrequest.
When successfully exploited, this vulnerability can lead to:
- Denial of service through worker process crashes
- 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
- Xint.io (finder)