NGINX2Root (CVE-2026-123007 and four related CVEs) is a set of five memory safety flaws in nginx that let an unauthenticated attacker crash nginx workers and, where address space layout randomization (ASLR) is off or bypassed, run code as the worker (write-up). Xint found and reported them. nginx fixed them in 1.31.9 and 1.30.7, released on November 18, 2026. Every nginx release from 0.5.33 to 1.31.8 is affected by at least one of them, depending on the configuration.
Update, November 18, 2026: nginx 1.31.9 and 1.30.7 are out and the official nginx images on Docker Hub carry them. Alpine 3.24 and edge ship nginx 1.30.7-r0. Debian, Ubuntu, Alpine 3.22 and 3.23 and OpenResty had not published fixed builds when we checked. The ingress-nginx controller is retired and will not get a fix; see the table below. After updating, restart nginx: a reload keeps old worker processes on existing connections.
Key highlights
- What it is: five flaws in nginx: CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425. Xint reports chaining them with a Linux kernel flaw to get root on the host.
- Severity: nginx rates CVE-2026-123007 and CVE-2026-113425 major and the other three medium.
- Affected: nginx 0.5.33 to 1.31.8, depending on the flaw and the configuration (1.9.5 to 1.31.8 for the main HTTP/2 flaw).
- Most exposed: internet-facing servers with HTTP/2 enabled, including every ingress-nginx controller that keeps its default settings.
- Fix: nginx 1.31.9 (mainline) or 1.30.7 (stable). Other distributions ship on their own schedule (see the table below).
- Stopgap: turn off HTTP/2 and HTTP/3, point
proxy_passat a fixed upstream group and keep the mail proxy off untrusted networks until you can update. - Exploitation: Xint does not report exploitation in the wild. None of the five CVEs is in the CISA KEV catalog (version 2026.11.18, checked November 18, 2026).
Who is exposed
Versions are from the nginx advisories and conditions from the Xint write-up:
| CVE | Exposed when | Affected versions |
|---|---|---|
| CVE-2026-123007 | HTTP/2 is enabled | 1.9.5 to 1.31.8 |
| CVE-2026-123633 | HTTP/2 is enabled and nginx proxies to an upstream | 1.19.7 to 1.31.8 |
| CVE-2026-121810 | HTTP/3 is enabled and nginx proxies to an upstream | 1.25.0 to 1.31.8 |
| CVE-2026-123634 | resolver is set, the proxy_pass target comes from the request and mirror runs with mirror_request_body off | 0.6.18 to 1.31.8 |
| CVE-2026-113425 | the mail proxy runs with proxy on and auth_http | 0.5.33 to 1.31.8 |
nginx also ships inside ingress controllers, whose version numbers differ from the nginx version they bundle. OpenResty versions follow nginx (1.31.8.1 bundles nginx 1.31.8). Xint has not published the final reproduction steps.
Fix status by distribution
Status as of November 18, 2026.
| Distribution | Status | Builds | Source |
|---|---|---|---|
| nginx.org | Fixed | 1.31.9 (mainline), 1.30.7 (stable) | nginx security advisories |
| Official nginx images on Docker Hub | Fixed | 1.31.9 and 1.30.7 tags; mainline, stable and latest updated the same day, so pull them again | Docker Hub |
| Alpine 3.24 and edge | Fixed | nginx 1.30.7-r0 | Alpine secdb |
| Alpine 3.22 and 3.23 | No fix yet | Alpine secdb | |
| Debian | No fix yet | nginx vulnerable in bookworm, trixie, forky and sid | Debian security tracker |
| Ubuntu | No fix yet | nginx vulnerable from 16.04 to 26.10 | Ubuntu CVE tracker |
| OpenResty | No fix yet | latest release 1.31.8.1 (nginx 1.31.8), October 2026 | OpenResty releases |
| ingress-nginx controller | No fix planned | retired; last release v1.15.1, March 2026 | ingress-nginx retirement |
How to check if you’re exposed
- Run
nginx -vin the container or on the host. Distribution packages can carry a fix under an older version, so compare the full package version with your distribution’s advisory linked in the table. - Run
nginx -T | grep -nE 'http2|http3|quic|resolver|mirror|auth_http'to see which of the conditions above your configuration meets. - For ingress-nginx, check the controller ConfigMap for
use-http2: "false". Without it, HTTP/2 is on.
How Cycode helps
Three items on the Threat Intelligence dashboard query the Context Intelligence Graph across connected repositories and scanned container images:
- Container images: lists images with nginx before 1.30.7 or from 1.31.0 to 1.31.8, whether it comes from an official nginx image, a Debian or Alpine package or the nginx built into ingress-nginx controller and OpenResty images. The count is the number of image repositories.
- Dockerfiles: lists Dockerfiles that build on an official nginx image in the affected range or on a floating tag, and on OpenResty or ingress-nginx controller images with any tag. A Dockerfile on a floating tag such as
lateststays listed until it pins nginx 1.30.7, 1.31.9 or later, because the tag does not show which version it pulled. - Kubernetes manifests: lists manifests with an ingress-nginx IngressClass or a workload that runs an ingress-nginx image.
An image match means the upstream nginx version is in the affected range; distribution packages with a backported fix still match until their fixed versions are published. Dockerfile and manifest matches show where to check the version. Exposure also depends on the configuration in the table above.
What to do
- Upgrade to nginx 1.31.9 or 1.30.7 and restart it.
- Rebuild every image that bundles nginx once its maintainer ships the fix. The ingress-nginx controller will not get one: plan a move to another ingress controller.
- Until you can upgrade, turn off HTTP/2: remove
http2fromlisten(on 1.25.1 and later also sethttp2 off;). Clients that need HTTP/2, such as gRPC, stop working. Turn off HTTP/3: remove the QUIC listeners, sethttp3 off;and clear theAlt-Svcheader. Pointproxy_passat a fixed upstream group and bind mail listeners to localhost. - Start with internet-facing nginx that serves HTTP/2.
Sources
- NGINX2Root write-up, Xint
- nginx security advisories
- CISA Known Exploited Vulnerabilities catalog
- CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, CVE-2026-113425