Tech

NGINX2Root: Five Critical NGINX Flaws Put 225 Million Websites at Risk

Five critical vulnerabilities in NGINX, the web server software behind more than 225 million websites, were disclosed on Wednesday 18 November 2026, and at least one lets an unauthenticated attacker run code on a vulnerable server without logging in. The flaws, collectively dubbed NGINX2Root, each carry a critical severity score of 9.2, and fixed versions were released on the same day.

F5, the company that maintains NGINX, published security advisories for all five flaws in an out-of-band release on 18 November. The most urgent, tracked as CVE-2026-123007, needs nothing more than HTTP/2 switched on to be reachable, and researchers have already published proof-of-concept code for it.

NGINX2Root at a Glance

ItemConfirmed detail
DisclosedWednesday 18 November 2026, by F5 in an out-of-band security release
FlawsFive critical vulnerabilities, collectively named NGINX2Root by researcher Xint (Theori)
SeverityCVSS v4.0 9.2 (Critical) for all five, per F5
Worst flawCVE-2026-123007 — unauthenticated remote code execution via HTTP/2 flow control
Sites affectedMore than 225 million sites run NGINX, per Netcraft’s September 2026 web server survey
Fixed versionsNGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), released 18 November 2026
Exploitation in the wildNone reported as of 18 November 2026; none of the five CVEs is on CISA’s Known Exploited Vulnerabilities catalog
Proof of conceptPublicly available on GitHub for CVE-2026-123007, published by Rapid7

The HTTP/2 Flaw That Needs Nothing but a Connection

CVE-2026-123007 is the flaw administrators should treat as the most urgent. It sits in NGINX’s HTTP/2 flow-control handling and affects NGINX Open Source releases from 1.9.5, which shipped in 2015, through 1.31.8. The only condition is that the server accepts HTTP/2 connections over TLS, which is the default posture for a large share of modern deployments.

Xint, the security researcher credited with finding the flaw, reported code execution over public HTTPS on major cloud platforms under normal concurrent traffic. Wiz Research independently confirmed that the flaw can be used to bypass address space layout randomisation, a protection that normally makes memory-corruption exploits far harder to land. Rapid7 published a proof-of-concept exploit aimed at a freshly started local target, which means defenders should assume working exploit code is now in circulation even though no attacks in the wild have been confirmed.

The flaw is separate from the NGINX vulnerabilities F5 disclosed in October, and from a separate HTTP/2 proxy weakness patched in June. Running a build newer than the October security release does not mean a server is safe: F5 lists NGINX Open Source 1.31.8 as affected, so only the November fixes close it.

The Other Four Flaws Behind the Same Release

The remaining four vulnerabilities are all memory-corruption flaws in NGINX worker processes, and each needs a specific configuration to be reachable. CVE-2026-123633 is a use-after-free bug in HTTP/2 handling that affects versions 1.19.7 to 1.31.8 and also requires the server to proxy requests to a backend while a worker runs low on connections. Wiz Research and Metnir both reported code execution through it in lab conditions.

CVE-2026-121810 is a use-after-free flaw in the HTTP/3 module, affecting versions 1.25.0 to 1.31.8 where HTTP/3 is enabled and NGINX proxies to an upstream. CVE-2026-123634 is a use-after-free flaw in the NGINX resolver, triggered when NGINX proxies to a server name containing variables. CVE-2026-113425 affects the mail proxy module and reaches back furthest, affecting versions from 0.5.33 to 1.31.8.

Xint also reported a separate, still-unpatched Linux kernel flaw — a use-after-free in the SCTP protocol implementation, with no CVE assigned as of 18 November — that can be chained with the NGINX flaws to escalate from worker-level access to full root on the host, including inside Docker containers. That chain is the reason for the NGINX2Root name.

225 Million Sites in the Blast Radius

NGINX is one of the two dominant web servers on the public internet, and Netcraft counted more than 225 million sites using it in its September 2026 survey. That scale is what turns five configuration-dependent flaws into a systemic event: the vulnerable population includes content delivery networks, hosting platforms, reverse proxies in front of applications, and the load balancers of major services.

The exposure is not evenly spread. Servers that never enabled HTTP/2 or HTTP/3 are not reachable through the two most dangerous flaws, and the mail-proxy flaw only matters to the small number of deployments running NGINX as a mail proxy. But HTTP/2 is now enabled by default on most managed hosting and cloud load-balancer setups, so the population at risk from CVE-2026-123007 alone is very large.

The disclosure also carries a warning for Kubernetes users: the ingress-nginx controller is retired and will not receive a fix, according to researchers tracking the release. Deployments still running it need a migration plan rather than a patch.

No Exploitation Seen Yet — and Why That Is Not Reassurance

As of 18 November, no source reviewed by Tenable reported exploitation of any of the five flaws in the wild, and none of the five CVEs appeared on CISA’s Known Exploited Vulnerabilities catalog. CERT-EU likewise reported no known exploitation on the day of disclosure. Xint found the bugs on 11 October and reported them to F5 through HackerOne on 16 October, giving vendors just over a month of coordinated disclosure before publication.

That clean record is reassuring only in a narrow sense. The publication of proof-of-concept code, the coordinated disclosure window closing, and the sheer number of exposed servers mean the window between disclosure and attempted exploitation is likely to be short. The pattern is familiar from earlier web-server flaws: patching lags disclosure, and scanners begin probing within days. The recent history of the web underlines the point — the Archive of Our Own security incident that took the site offline for 17 days showed how a single infrastructure weakness can shut a major service down for weeks, and Britain’s cyber chief warned AI will accelerate attacks on critical infrastructure, with software flaws discovered and exploited at a scale that was once unimaginable.

What Site Owners and Hosts Must Do Today

The fix itself is straightforward: upgrade NGINX Open Source to 1.30.7 on the stable branch or 1.31.9 on the mainline branch, and check the F5 advisories for the matching NGINX Plus builds. One operational detail matters: running “nginx -s reload” does not load the new binary, so the server process must be restarted or its binary upgraded after updating, or the old vulnerable code keeps running.

Until an upgrade is possible, switching HTTP/2 off closes the two HTTP/2 flaws, which removes the most widely exposed attack path. WordPress site owners should note that updating WordPress, plugins or themes will not patch NGINX — the flaw is in the server software beneath the site, so the fix has to come from the hosting provider or the server administrator. Wordfence, which flagged the flaws for WordPress owners, advises checking with the hosting provider about whether its servers are affected and patched.

Administrators should also check the advisories for the five additional, lower-severity NGINX flaws fixed in the same 18 November release, and confirm their build covers both CVE-2026-123007 and CVE-2026-123633 rather than only one of them.

Frequently Asked Questions

Is NGINX2Root being exploited right now? No exploitation in the wild had been reported as of 18 November 2026, and none of the five CVEs was on CISA’s Known Exploited Vulnerabilities catalog. Proof-of-concept code is public, so that position can change quickly.

Which NGINX versions are affected? It depends on the flaw. CVE-2026-123007 affects 1.9.5 to 1.31.8; CVE-2026-123633 affects 1.19.7 to 1.31.8; CVE-2026-121810 affects 1.25.0 to 1.31.8; CVE-2026-113425 reaches back to 0.5.33. Every release up to 1.31.8 is affected by at least one of the five.

What are the fixed versions? NGINX Open Source 1.30.7 (stable branch) and 1.31.9 (mainline branch), both released on 18 November 2026. NGINX Plus builds are covered by the matching F5 advisories.

Does turning off HTTP/2 protect my server? It closes the two HTTP/2 flaws, including the most urgent one, CVE-2026-123007. It does not address the HTTP/3, resolver or mail-proxy flaws, so it is a mitigation, not a fix.

Will updating WordPress fix this? No. The vulnerabilities are in NGINX itself, not in WordPress, its plugins or its themes. Only updating NGINX, or asking the hosting provider to do so, removes the risk.

Myth to retire: the idea that a server is safe because it was patched in October. F5’s October release fixed different NGINX flaws, and version 1.31.8 — newer than that release — is listed as affected by the November flaws. Only the 18 November fixes close NGINX2Root.

Julian Vance

Julian Vance is a senior technology analyst and engineering correspondent covering the evolution of consumer electronics and industrial tech. His reporting cuts through corporate jargon to deliver data-backed hardware and software evaluations.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button
×

Stay Updated!

Get our latest news and updates first on Google.

Add as a preferred source on Google