nginx runs roughly a third of the web. On November 18, 2026, researchers disclosed five critical vulnerabilities in it — plus a Linux kernel bug that chains them into full root access. The worst flaw needs nothing but HTTP/2 turned on, and it has been hiding in the code since 2015. Here is what nginx2root is, who is affected, and exactly what to patch.
product:nginx on Shodan before disclosure; 98.9% of nginx servers with a known version were running a vulnerable release. As of November 19, Censys counted about CVE-2026-123007 sits in nginx's HTTP/2 flow-control code — the part that manages how much data a client may send. An unauthenticated remote attacker can corrupt memory in an nginx worker, leak memory addresses to bypass ASLR, and overwrite a pointer to a cleanup function that fires when a connection closes. The result: commands executed with worker privileges, with output returned over the existing connection.
Xint demonstrated the exploit over the public internet against servers on AWS, GCP, and Azure. The bug has existed since nginx added HTTP/2 support in version 1.9.5 — eleven years ago. As Security Affairs noted, pre-auth RCE in nginx almost never happens; the last known one dates to 2013, despite two decades of fuzzing and auditing by the world's best researchers.
| CVE | Bug class | Affected configuration |
|---|---|---|
| CVE-2026-123007 | Integer overflow, out-of-bounds heap read/write | HTTP/2 enabled (since 1.9.5, 2015) |
| CVE-2026-123633 | Use-after-free | HTTP/2 with `proxy_pass` to a backend |
| CVE-2026-121810 | Use-after-free | HTTP/3 (QUIC) with `proxy_pass` |
| CVE-2026-123634 | Use-after-free | resolver +proxy_pass with variables + subrequest |
| CVE-2026-113425 | Use-after-free | Mail proxy with proxy on andauth_http |
F5's November 18 out-of-band release fixed all five, plus five additional nginx flaws — including CVE-2026-118899, an infinite loop while reading a request body over TLS 1.3. The kernel SCTP flaw that chains the nginx bugs to root has no CVE and no patch yet; Xint is withholding most technical details pending a kernel fix. That means patching nginx removes the remote entry point, but not the step to root — patch now, and watch for the kernel fix.
The discovery story is the real headline for developers. nginx has been fuzzed by the best researchers for two decades, and an AI-assisted research effort found not one but five pre-auth flaws plus a kernel chain. Xint found the bugs on October 11, 2026, reported them to F5 via HackerOne on October 16, and published after coordinated disclosure on November 18.
This is the same pattern we saw two days earlier with Java4Shell — an AI-found critical flaw in OpenJDK's Base64 decoder. AI is now doing what two decades of human auditing could not: finding memory-corruption bugs in the most-scrutinized infrastructure code on earth. The defensive lesson is the same in both cases: patch fast, because the attackers now have AI too.
nginx -v. Unpatched builds of NGINX Open Source from 1.9.5 through 1.31.8 are in scope when HTTP/2 is enabled.
No active exploitation had been reported at the time of disclosure, and CVE-2026-123007 was not yet on CISA's Known Exploited Vulnerabilities catalog. But a public proof-of-concept is already on GitHub. The window between disclosure and mass exploitation is measured in days, not weeks.
Originally published on AI Growth Lab.