NGINX2Root is the name the security company Xint has given to five critical flaws in the NGINX web server that let an attacker run code on the server without logging in. The most dangerous one, CVE-2026-123007, is present in every official release from 1.9.5 to 1.31.8 and needs nothing more than HTTP/2 to be enabled. The fixes shipped on November 18, 2026, in NGINX 1.30.7 and 1.31.9. Debian and Ubuntu have since released fixed packages for their supported versions. Anyone running NGINX should now check that the updates are actually installed and that the processes have been restarted. For the second half of the attack chain, a flaw in the Linux kernel, there is no fix yet.
What NGINX2Root is
NGINX is one of the most widely used web servers and reverse proxies in the world. According to Xint’s write-up, each of the five flaws leads to code execution with the privileges of the NGINX worker process on its own. They do not need to be chained, but they affect different configurations. According to F5, the company behind NGINX, all five score 8.1 under CVSS 3.1 and 9.2 under CVSS 4.0. All of them are data-plane bugs, and the control plane is not affected.
- CVE-2026-123007: an HTTP/2 flow-control overflow that leads to a heap buffer overflow. Any server with HTTP/2 enabled is affected, going back to version 1.9.5 from 2015.
- CVE-2026-123633: a use-after-free in HTTP/2 when requests are forwarded to a backend server, from version 1.19.7.
- CVE-2026-123634: a use-after-free in the DNS resolver when the proxy_pass destination is built from variables and subrequests are created, for example via mirror or SSI, from version 1.13.4.
- CVE-2026-121810: a use-after-free in HTTP/3 with forwarding to a backend, from version 1.25.0.
- CVE-2026-113425: a use-after-free in the mail proxy when proxy on and auth_http are used, from version 0.5.15.
The nginx.org security advisories and the 1.30.7 release notes also list four more flaws fixed in the same versions, including an infinite loop while reading request bodies over TLS 1.3 (CVE-2026-118899) and a buffer overflow when alias and try_files are combined (CVE-2026-125283). In total, the update fixes nine CVEs. For NGINX Plus, versions 37.3.0.1 and 37.0.8.1 are fixed.
Why CVE-2026-123007 affects so many servers
HTTP/2 uses flow-control windows to govern how much data a peer may send. The protocol caps these windows at 31 bits. According to Xint, NGINX lets a send window grow past that cap under certain conditions, when the same queued credit is returned twice. A later check on the oversized value then underflows, and NGINX copies data with an invalid length past the end of a buffer. According to the researchers, a server delivering ordinary static files over HTTP/2 is enough for an attack. No vulnerable application or third-party module is required.
Xint estimated how widespread the problem is using the Shodan search engine. On November 10, it returned 56.7 million hosts running NGINX. For 11.94 million of them a version was identifiable, and 98.9 percent of those fell within the vulnerable range of 1.9.5 to 1.31.8. That does not prove they can be attacked, because HTTP/2 has to be enabled and distributions often backport fixes without changing the version number. But it shows how few public servers report a current release.
A Xint researcher found the flaw while preparing for the ZeroDay Cloud 2026 competition. According to the company, a fully automated scan found the other four a few days later without human guidance. According to Sysdig, several teams discovered the HTTP/2 bugs independently. Xint and the security company Wiz say they have built working exploits that bypass ASLR memory protection. No public proof of concept or in-the-wild exploitation was known as of November 19.
The road to root: the kernel flaw
An NGINX worker normally runs with limited privileges. The step to root comes from a second, previously unknown flaw in the Linux kernel, which Xint found in the send path of the SCTP network protocol. It has been in the code since kernel 4.15 from 2018. Because containers share the kernel with the host, Xint also managed to break out of a Docker container running the official NGINX image and gain root on the host system. Many distributions install the SCTP module by default and load it automatically as soon as a program opens an SCTP socket. At the time of disclosure, there was no CVE number and no kernel fix.
This is reminiscent of the critical Apache HTTP/2 flaw just over a week ago: once again, the implementation of a widely used protocol in a core web server is the point of attack.
Debian and Ubuntu ship fixes
For operators using distribution packages, one point matters: the version that nginx -v prints says nothing about the patch level. What counts is the full package version. According to the Debian Security Tracker, CVE-2026-123007 is fixed in Debian 13 with DSA-6642-1 (package 1.26.3-3+deb13u11) and in Debian 12 with DLA-4918-1 (1.22.1-9+deb12u11). Ubuntu lists fixed packages for 24.04 LTS (1.24.0-2ubuntu7.20), 22.04 LTS (1.18.0-6ubuntu14.23) and 26.04 LTS (1.28.3-2ubuntu1.13), among others. For 20.04 and 18.04, fixes are available through Ubuntu Pro.
Container images are only safe once they have been rebuilt on a fixed version and redeployed. Updating the host does not change a running container. According to Sysdig, the Kubernetes project ingress-nginx, which was archived in March 2026 and ships its own NGINX build, will not receive these fixes. Anyone still using it should plan a migration.
What admins should do now
- Update and restart: move to NGINX 1.30.7 or 1.31.9, or the fixed distribution package. Then restart NGINX instead of just reloading it, so that no worker keeps running the old binary.
- Turn off HTTP/2 temporarily: where updating is not yet possible, disabling HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633. On NGINX 1.25.1 and later, use http2 off; in every affected server block; on older versions, remove http2 from the listen directive. The other three flaws remain open.
- Review other features: disable HTTP/3 if it is not needed, point proxy_pass at fixed upstream groups instead of variables, use mirror and SSI only where necessary, and restrict the mail proxy to trusted sources.
- Block SCTP: on hosts and Kubernetes nodes that do not need SCTP, block the kernel module, for example with a file in /etc/modprobe.d/. That also applies to NGINX servers that are already patched, as long as the kernel fix is missing.
If you run WordPress behind NGINX, this is also a good moment to check the application itself. We covered the latest security update in our article on WordPress 7.1.5.
Our take
NGINX2Root has two halves. The NGINX half is a classic patching job: fixes have been available for four days, the major distributions have followed, and effective configuration changes exist for the meantime. The kernel half is the bigger problem, because it turns a flaw with limited privileges into full control of the host, and there is no fix for it yet. The way the flaws were found also stands out: an automated scan discovered four of the five. That fits a trend we have been seeing more often. Automated and AI-assisted tools are finding bugs in code that was long considered well reviewed, and they shorten the time operators have to patch.


