nginx2root (CVE-2026-123007): what it is, who is exposed, and what to do today The Rokkhe research team compiled a consolidated advisory on nginx2root, a set of five unauthenticated memory-corruption bugs in nginx disclosed by Xint researchers and fixed in nginx 1.31.9 and 1.30.7 on 18 November 2026. The most serious, CVE-2026-123007, is an HTTP/2 flow-control flaw present in every nginx release since 1.9.5 in 2015 that lets an attacker crash a worker and, in researchers' tests, run code even on static-file-only servers. The team advises operators to locate all nginx instances including containers, ingress controllers and appliances, update and restart them, and disable HTTP/2 on any listener they cannot patch immediately. This article was first published on the Rokkhe blog on Hashnode https://rokkhe.hashnode.dev/nginx2root-cve-2026-123007-nginx-http2-rce . It was drafted with AI assistance and reviewed and edited by the Rokkhe team; all facts were checked against the linked public sources as of 20 Nov 2026. What is known about nginx2root CVE-2026-123007 and four related nginx bugs as of 20 Nov 2026, from 40+ public sources. By the Rokkhe research team. On 18 November 2026, nginx.org released nginx 1.31.9 mainline and 1.30.7 stable with fixes for ten security bugs nginx news https://nginx.org/ , nginx advisories https://nginx.org/en/security advisories.html . Five of them are memory corruption bugs that an unauthenticated attacker can use to crash an nginx worker and, in researchers' tests, run code on the server. Xint, one of the teams that found them, calls the set nginx2root Xint https://xint.io/blog/nginx2root-remote-code-execution . The one that matters for most people is CVE-2026-123007 , a flaw in HTTP/2 flow control that has been in every nginx release since HTTP/2 support arrived in 1.9.5 in 2015 Xint https://xint.io/blog/nginx2root-remote-code-execution , Rapid7 https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/ . If you run nginx with HTTP/2 turned on, this post is for you. We read the nginx changelog and fix commits, the researcher write-ups, the F5, distribution and government advisories, the security vendor analyses, the news and the discussion, and put it in one place. Every claim links to where it came from. Where sources disagree, we say so. The short version: find every nginx you run, including the ones inside containers, ingress controllers and appliances, update it, restart it, and turn HTTP/2 off on any listener you cannot patch today. Credit first. Xint researchers found all five memory bugs: one researcher found CVE-2026-123007 by hand and an automated Xint scan found the other four Xint https://xint.io/blog/nginx2root-remote-code-execution , Cloudflare https://blog.cloudflare.com/nginx2root/ . The two HTTP/2 bugs were also found independently by Wiz Research, Rapid7 Stephen Fewer , Ikotas Labs, Metnir and Palo Alto Networks Unit 42 Wiz https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities , Rapid7 https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/ , Cloudflare https://blog.cloudflare.com/nginx2root/ . The other five fixes in the release credit Marc Luchian and Liviu-Alexandru Bud, CERT.PL, ruokeqx, Vivek Parikh of BreachX Zero Day Labs and Maxim Dounin nginx CHANGES https://nginx.org/en/CHANGES . Thanks also to the nginx and F5 teams for shipping fixes for all of it in one release. Each bug is a separate way in. They do not need to be chained, and each one needs a different feature turned on Xint https://xint.io/blog/nginx2root-remote-code-execution , Cloudflare https://blog.cloudflare.com/nginx2root/ . | CVE | What it is | What has to be turned on | Affected open source versions | |---|---|---|---| | CVE-2026-123007 | HTTP/2 flow-control memory corruption | HTTP/2 on a listener. Works even when nginx only serves static files | 1.9.5 to 1.31.8 | | CVE-2026-123633 | HTTP/2 use-after-free | HTTP/2, proxying to a backend, and a worker running low on worker connections | 1.19.7 to 1.31.8 | | CVE-2026-121810 | HTTP/3 use-after-free | HTTP/3 QUIC , proxying to a backend | 1.25.0 to 1.31.8 | | CVE-2026-123634 | Resolver use-after-free | resolver , a proxy pass built from request data, and a subrequest such as mirror or SSI | 0.6.18 to 1.31.8 | | CVE-2026-113425 | Mail proxy use-after-free | a mail block with proxy on and auth http . No valid login needed | 0.5.33 to 1.31.8 | Sources: nginx advisories https://nginx.org/en/security advisories.html , CERT-EU https://www.cert.europa.eu/publications/security-advisories/2026-022/ , JFrog https://research.jfrog.com/post/nginx2shell-all-you-need-to-know-about-cve-2026-123007-and-cve-2026-123633/ , Red Hat https://access.redhat.com/security/vulnerabilities/RHSB-2026-019 . F5 rates all five 9.2 Critical under CVSS 4.0 and 8.1 High under CVSS 3.1, and says code execution needs ASLR to be off or bypassed NVD https://nvd.nist.gov/vuln/detail/cve-2026-123007 , Censys https://censys.com/advisory/nginx2root/ . Xint reports code execution as the nginx worker for each of the five, including leaking addresses to get past ASLR Xint https://xint.io/blog/nginx2root-remote-code-execution , Hadrian https://hadrian.io/vulnerability-alerts/nginx-cve-2026-123007-remote-code-execution-confirmed . HTTP/2 lets a client tell the server how much response data it may send before waiting. nginx keeps a running counter of that allowance for each connection, and the protocol caps it at 2^31 minus 1 bytes Rapid7 https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/ . When a client cancels a stream that still has data queued, nginx gives the unsent allowance back to the counter. That refund had no upper-bound check. A client can grant the same amount once with a WINDOW UPDATE frame and then get it refunded a second time by cancelling, which pushes the counter past the cap Xint https://xint.io/blog/nginx2root-remote-code-execution . From there, the check on later WINDOW UPDATE frames wraps around, the oversized counter turns into a negative length when nginx prepares data to send, and the TLS layer copies memory out of bounds. That can leak memory and corrupt the heap JFrog https://research.jfrog.com/post/nginx2shell-all-you-need-to-know-about-cve-2026-123007-and-cve-2026-123633/ , Rapid7 https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/ . The fix is small: nginx now tracks data already queued for sending and counts it when it validates a WINDOW UPDATE, so the counter can no longer pass the cap commit b89c410 https://github.com/nginx/nginx/commit/b89c4100bf6762a45e4a6463eaf4b70368277c94 , JFrog https://research.jfrog.com/post/nginx2shell-all-you-need-to-know-about-cve-2026-123007-and-cve-2026-123633/ . Cloudflare built 1.31.8 and 1.31.9 with AddressSanitizer and saw four of the five bugs fault on 1.31.8 and run clean on 1.31.9 Cloudflare https://blog.cloudflare.com/nginx2root/ . Harder than "send one request", easier than you would like. memcpy . StepSecurity reports that the exploit's instructions say earlier tests failed on servers already handling heavy traffic, and notes the bug itself does not need AVX-512: it crashed a worker on a CPU without it Xint also found a use-after-free in the Linux kernel's SCTP code, present since Linux 4.15 2018 . Code already running as the nginx worker can use it to become root on the host, and Xint did this from nginx inside a Docker container Xint https://xint.io/blog/nginx2root-remote-code-execution , LWN https://lwn.net/Articles/1108362/ . Many distributions load the SCTP module automatically the first time a program opens an SCTP socket, so hosts that never use SCTP can still be exposed. In Sysdig's lab, one SCTP socket opened from the worker was enough to load it Sysdig https://www.sysdig.com/blog/nginx2root . As of 18 to 19 Nov there was no CVE and no kernel fix, and Xint is holding back details until there is one Cloudflare https://blog.cloudflare.com/nginx2root/ , Sysdig https://www.sysdig.com/blog/nginx2root . Not that anyone has confirmed, as of 20 Nov. Five teams found the same HTTP/2 bugs independently, several with AI-assisted code analysis JFrog https://research.jfrog.com/post/nginx2shell-all-you-need-to-know-about-cve-2026-123007-and-cve-2026-123633/ , Wiz https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities . Plan as if someone who does not publish found them too. Work through these on every host and container that runs nginx. The nginx commands below were tested on Debian 13 with nginx 1.26.3. 1. Find every nginx. That includes distribution packages, nginx.org packages, official and third-party container images, Kubernetes ingress controllers, OpenResty, NGINX Plus, and appliances that ship nginx inside Cloudflare https://blog.cloudflare.com/nginx2root/ , JFrog https://research.jfrog.com/post/nginx2shell-all-you-need-to-know-about-cve-2026-123007-and-cve-2026-123633/ . OpenResty 1.31.8.1 is built on nginx 1.31.8 and is affected until it ships a new build OpenResty issue 1165 https://github.com/openresty/openresty/issues/1165 . Hosts pgrep -a nginx Kubernetes: images that look like nginx kubectl get pods -A -o jsonpath='{range .items }{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.spec.containers .image}{"\n"}{end}' | grep -iE 'nginx|openresty|ingress' 2. Check the version and the full package version. nginx -v Debian / Ubuntu dpkg-query -W -f='${Package} ${Version}\n' 'nginx ' RHEL / Fedora / Amazon Linux rpm -q nginx Alpine apk info -v nginx Inside a container or pod docker exec