NGINX has patched nginx2root, a set of five memory-corruption flaws that let unauthenticated attackers run code on NGINX servers, and a working public exploit for the most serious of them, CVE-2026-123007, appeared on GitHub the same day.
CVE-2026-123007 is an integer underflow in NGINX’s HTTP/2 flow-control code that leads to an out-of-bounds memory copy. F5 rates it 9.2 under CVSS 4.0, and the bug has been in every official NGINX release from 1.9.5, the 2015 version that introduced HTTP/2, through 1.31.8. A second HTTP/2 flaw, CVE-2026-123633, is a use-after-free that has existed since NGINX 1.19.7 and carries the same 9.2 score.
The name nginx2root comes from Xint, which disclosed five NGINX bugs on Wednesday, November 18, and chained the HTTP/2 flaw with an unpatched Linux kernel SCTP bug to go from an anonymous web visitor to root on the host.
Wiz Research separately reported remote code execution with ASLR defeated on an NGINX server serving content directly, with no backend application and no third-party modules.
As of November 18, fixed releases are out for NGINX Open Source (1.30.7 stable and 1.31.9 mainline) and NGINX Plus (37.0.8.1 and 37.3.0.1), but NGINX Plus R34 through R36 have no fix, and major Linux distributions had not shipped patched packages.
The Five nginx2root Vulnerabilities
Xint’s nginx2root disclosure covers five NGINX CVEs, each of which gives code execution with NGINX worker privileges in a different configuration. Xint said, “each one leads to remote code execution on its own.”
CVE-2026-123007 hits any server with HTTP/2 enabled. CVE-2026-123633 needs HTTP/2 plus a reverse-proxy (upstream) setup. CVE-2026-123634 is a use-after-free in the DNS resolver reached through proxy_pass with a request-derived variable, a resolver and the mirror directive. CVE-2026-121810 is a use-after-free in HTTP/3 (QUIC) stream handling with upstream forwarding, and CVE-2026-113425 is a use-after-free in the mail proxy’s auth_http authentication path.
Only the two HTTP/2 bugs are stopped by turning HTTP/2 off. The nginx.org release that fixes all five, 1.31.9 and 1.30.7, closes ten CVEs in total, including an infinite loop when reading request bodies over TLS 1.3 (CVE-2026-118899).
How the NGINX HTTP/2 Flaws Work
CVE-2026-123007 sits in HTTP/2 flow control, the mechanism that lets a client tell the server how much data it may send. NGINX deducts from the connection’s send window when it queues response data and adds the allowance back when a stream is cancelled, but it does that refund without checking the HTTP/2 maximum, so the window (h2c->send_window) can grow past its legal limit.
Once the window is over the maximum, the bounds check in ngx_http_v2_state_window_update() wraps around as unsigned arithmetic, and NGINX accepts further WINDOW_UPDATE frames. The oversized value is later converted to a negative off_t, which produces a malformed buffer and an out-of-bounds memcpy() in the TLS send path, according to Xint and Wiz.
CVE-2026-123633 is a lifetime bug. An HTTP/2 connection with no active streams is marked as reusable, while a HEADERS frame is only partially received, and NGINX does not remove it from the reusable list when a request stream is created. When connection slots run low, NGINX can close that connection mid-request, freeing memory the upstream proxy code is still using. Wiz said the use-after-free has been present for nearly six years.
How Researchers Defeated ASLR and Reached Root
F5’s advisory says code execution requires ASLR (address space layout randomisation) to be disabled or bypassed. All three teams that published details say they bypassed it.
For CVE-2026-123007, the same malformed copy leaks 64 bytes of NGINX image and heap pointers inside the TLS response, and Xint uses those addresses to overwrite a cleanup function pointer. Xint said the exploit worked on AWS, Google Cloud, and Azure, over public HTTPS endpoints and under normal concurrent traffic. Wiz confirmed code execution on official NGINX 1.31.7 and 1.31.8 builds over TLS on 64-bit systems.
Xint then chained the NGINX foothold with a use-after-free in the Linux kernel’s SCTP code, introduced in Linux 4.15 in 2018. In Xint’s tests, an attacker running as the NGINX worker reliably gained root, including from inside a Docker container. No kernel patch or CVE ID for the SCTP bug was public at the time of disclosure, and Xint withheld most of its details.
Five teams found the HTTP/2 bugs independently: Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint. Xint said one of its researchers found CVE-2026-123007 while preparing for ZeroDay Cloud 2026, and a fully automated Xint scan found the other four. Wiz said its Atlas AI code-scanning harness found both HTTP/2 flaws. Ikotas Labs announced the HTTP/2 bug as NGINX2Shell.
Why the Severity Ratings Differ
F5 scores all five nginx2root CVEs 9.2 (Critical) under CVSS 4.0 and 8.1 (High) under CVSS 3.1. Rapid7 lists the CVSS 4.0 vector for CVE-2026-123007 as AV:N/AC:H/AT:P/PR:N/UI:N, meaning it is network-reachable and unauthenticated, but with high attack complexity and specific preconditions.
The nginx security advisories page uses its own scale and rates CVE-2026-123007 as “major” and the mail-proxy flaw as “major”, and the other three as “medium”. Red Hat rates CVE-2026-123007 as Critical, with a CVSS score of 8.1, according to Precursor Security’s live tracker, and Ubuntu rates it as High priority.
Which NGINX Versions and Distributions Have a Fix
| Product | Status as of Nov 18, 2026 | Fixed version or note |
|---|---|---|
| NGINX Open Source stable | Fixed | 1.30.7 |
| NGINX Open Source mainline | Fixed | 1.31.9 |
| NGINX Plus 37.x | Fixed | 37.0.8.1 / 37.3.0.1 (CVE-2026-123633: 37.0.7.1 / 37.2.0.1) |
| NGINX Plus R34–R36 | No fix listed | Move to a fixed 37.x build |
| Ubuntu | Fix needed, none shipped | Supported releases from 16.04 on marked “needed” |
| RHEL 8, 9, 10 | Under investigation | No erratum yet |
| Debian, SUSE, Amazon Linux, Alpine | No fixed package reported | Watch vendor trackers |
| NGINX Ingress Controller | Fixed in 5.8.0 | 2026-lts-r11 not fixed |
| Community ingress-nginx | No patch coming | Project archived |
F5 published separate advisories for CVE-2026-123007 (K000163926) and CVE-2026-123633 (K000163928). F5 says BIG-IP, BIG-IQ, F5OS, BIG-IP Next for Kubernetes, and F5 AI Gateway are not affected.
Distribution status above comes from Precursor Security and Upwind, which also report that NGINX forks such as OpenResty, Tengine, Angie, and freenginx still contain the vulnerable code. The community ingress-nginx project bundles NGINX 1.27.1 with HTTP/2 on by default and, being archived, will not receive a fix, according to Upwind and Aikido.
Xint counted 56.7 million NGINX hosts on Shodan as of November 10. Of the 11.94 million with an identifiable version, 98.9% fell in the CVE-2026-123007 range, though Xint cautions that a version banner does not confirm a host is exploitable.
Is CVE-2026-123007 Being Exploited?
No vendor or researcher has reported in-the-wild exploitation of any nginx2root flaw, and none had been added to CISA’s Known Exploited Vulnerabilities catalogue on November 18.
Exploit code for CVE-2026-123007 is public. Rapid7 researcher Stephen Fewer published a crash trigger and a full RCE chain on GitHub alongside Rapid7’s analysis, demonstrating unauthenticated code execution against a linux/amd64 Docker image of NGINX 1.31.8 with HTTP/2 and TLS enabled.
Rapid7’s exploit has real limits. It needs roughly 128 GB of HTTP/2 traffic over a single connection, about two minutes at 10 Gbit/s or 17 minutes at 1 Gbit/s, and links slower than about 300 Mbit/s would likely hit NGINX’s default one-hour connection limit. It also depends on a glibc memory-copy routine that is selected only on CPUs with AVX-512, and Rapid7 says proxied HTTP/2 connections likely won’t carry the needed frames.
Wiz and Xint have both withheld their full exploits. Precursor Security warned that fake nginx2root exploits are circulating on GitHub and that Rapid7’s repository is the only genuine public PoC it knows of.
What NGINX Admins Should Do Now
Upgrade NGINX Open Source to 1.30.7 or 1.31.9, or NGINX Plus to 37.0.8.1 or 37.3.0.1, then restart the service with systemctl restart nginx. Xint notes that a reload leaves old worker processes serving existing connections, so a full restart is needed to remove vulnerable code from memory.
Check the running version with nginx -v and find HTTP/2 and QUIC listeners with grep -RnE "http2|quic" /etc/nginx/. On distribution packages, compare the full version from dpkg -l nginx or rpm -q nginx against the vendor advisory, since Ubuntu, Debian and Red Hat usually backport fixes without changing the upstream version number.
If you cannot patch, Wiz and Xint recommend disabling HTTP/2: set http2 off; on NGINX 1.25.1 and later, or remove http2 from listen directives on older builds, then restart. That blocks CVE-2026-123007 and CVE-2026-123633 only. For ingress-nginx, Upwind recommends setting use-http2: "false" in the controller ConfigMap.
For the other three flaws, Xint lists disabling HTTP/3 (remove quic listeners and set http3 off), using fixed upstream groups instead of request-time DNS lookups with mirror, and binding mail-proxy listeners to loopback or firewalling them. On hosts that do not need SCTP, Xint suggests blocking the kernel module with install sctp /bin/false in /etc/modprobe.d/, which does not unload a module that is already loaded.
Wiz says CDNs or WAFs that terminate HTTP/2 before traffic reaches NGINX may partly mitigate the HTTP/2 bugs. It suggests investigating unexpected NGINX worker crashes, NGINX-spawned commands, and long-lived HTTP/2 connections that push unusually large amounts of data.
Community Discussion
Join the conversation. Ask questions, share solutions, and help others.
Be the first to start the discussion!
