NGINX2Root: Five nginx Bugs Disclosed Today, Including an HTTP/2 Remote Code Execution Flaw Present Since 2015. The Fixed Release Isn't Out Yet. Turn Off HTTP/2 Where You Can, and Restart
If you run nginx with HTTP/2 on and it faces the internet, decide today whether you can turn HTTP/2 off until a fixed release ships. Researchers at Xint published five nginx bugs on November 18. The worst, CVE-2026-123007, is an integer overflow in HTTP/2 flow control that they say gives remote code execution with no login, in every official release from 1.9.5 (2015) through 1.31.8. Their timeline says the fixed release, nginx 1.31.9, is scheduled for November 19 Korean time, which is Wednesday evening or Thursday in the US. When we checked nginx.org this morning, there was no advisory for these CVEs and no 1.31.9 in the changelog.
So right now the only defense is configuration.
The five bugs, per Xint
All of this comes from Xint's write-up. nginx and F5 had not published their own descriptions, severities or CVSS scores where we could read them. F5's support article for the set wouldn't render for us.
CVE-2026-123007, HTTP/2 flow control integer overflow leading to heap corruption. Needs HTTP/2 enabled. Affects 1.9.5 through 1.31.8. Turning HTTP/2 off blocks it.
CVE-2026-123633, use-after-free when an HTTP/2 connection closes during an upstream connect. Needs HTTP/2 over TLS and proxy_pass. From 1.19.7. Turning HTTP/2 off blocks it.
CVE-2026-123634, use-after-free in the DNS resolver path. Needs a resolver, a proxy_pass built from the request (such as http://$host) and the mirror module. From 1.13.4.
CVE-2026-121810, use-after-free in HTTP/3 (QUIC). Needs HTTP/3 and an upstream. From 1.25.0.
CVE-2026-113425, use-after-free in the mail proxy's auth_http path. Needs a mail block with proxy and auth_http. From 0.5.15.
Xint says each gave it code execution as the nginx worker user in its test setups, with demos on AWS, Google Cloud, Azure and bare metal. It also says it chained one with a Linux kernel bug in SCTP to get root on the host and to escape a Docker container. It has deliberately left out the final steps needed to reproduce the full exploits, and we found no public exploit code. No exploitation in the wild has been reported.
Xint says one researcher found CVE-2026-123007 while preparing for a hacking competition, and that "a fully automated Xint scan" found the other four "without human guidance." It is the second big web server this month with an HTTP/2 remote code execution flaw, after Apache's mod_http2 (CVE-2026-119618).
What to do today
Find your nginx. Reverse proxies, load balancers, Kubernetes ingress controllers (ingress-nginx), container images, appliances and control panels often ship it. Run "nginx -V" on each and note the version and the modules.
Check whether HTTP/2 is on. Look for "http2" on a listen line, or "http2 on;" in a server block.
Turn HTTP/2 off where you can. On nginx 1.25.1 or later, set "http2 off;" in each server block and remove http2 from listen lines. On older versions, remove http2 from the listen lines. Xint warns that gRPC clients will break, because gRPC needs HTTP/2. Most websites keep working over HTTP/1.1, just a little slower.
Restart, don't reload. Xint points out that a reload leaves old workers handling existing HTTP/2 connections. Do a full restart and confirm no worker shows "shutting down."
Close the rarer paths. Turn off HTTP/3 and QUIC if you don't need them ("http3 off", remove quic listeners, block UDP 443). Point proxy_pass at fixed upstreams rather than request-built names. Bind mail proxy listeners to localhost or firewall them.
Install 1.31.9 or your distribution's fixed package when it ships, then restart again. Distributions often backport fixes without changing the version number, so check the package changelog, not just "nginx -v."
If you sit behind a CDN, check whether the CDN speaks HTTP/2 to your origin or only to visitors. Many speak HTTP/1.1 to the origin, which narrows exposure but isn't a fix. If your origin is reachable directly from the internet, the CDN doesn't protect it at all.
What is not known
The fixed version for the stable 1.30 branch; Xint names only 1.31.9. Whether the default nginx configuration from each distribution turns HTTP/2 on. Whether nginx Plus and F5 products built on nginx are affected; F5's article wasn't readable to us. CVSS scores.
What our edge can see
Nothing useful. These bugs live in HTTP/2 and HTTP/3 frame handling, below the level our sensors record. We make no claim about scanning for them either way.
How we know
We read Xint's write-up, nginx.org's security advisories page and the nginx changelog on November 18, 2026. The advisories page listed none of these CVEs, and the newest changelog entry was 1.31.8 from October 21. The descriptions above are Xint's and are not yet confirmed by nginx or F5. We'll update this post when the release and advisory appear.
Sources
Xint, "NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching," xint.io, November 18, 2026.
nginx.org security advisories and CHANGES, read November 18, 2026.
F5 support article K000164058 (linked by Xint; did not render for us).
Our earlier post on Apache's HTTP/2 flaw: Apache httpd mod_http2 CVE-2026-119618.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.



Comments