nginx2root: Is Your Website Host Running the Flawed nginx?
On November 18, nginx published fixes for a critical flaw, CVE-2026-123007, nicknamed “nginx2root.” It lets an attacker run code on a web server without logging in. It only applies when HTTP/2 is turned on.
Your site is affected only if the server that delivers it runs nginx. Your host knows. You can ask.
What nginx is
nginx is web server software. It often sits in front of websites, handing pages to visitors. Hosting companies and content delivery networks (CDNs) use it a lot, so you may be running on it without ever seeing it.
What the flaw does
HTTP/2 is the modern way browsers and servers talk. The flaw is in how nginx tracks how much data it may send over an HTTP/2 connection. A bad calculation corrupts memory. Rapid7 showed that this can let an attacker run code with the permissions of the nginx worker process.
The facts from nginx, Rapid7 and CERT-EU:
- Severity: Rapid7 and The Hacker News report a 9.2 out of 10 on CVSS v4, the standard severity score.
- Age: it has been in nginx since version 1.9.5, released in September 2015.
- Login: none needed.
- Condition: HTTP/2 must be enabled.
- Exploit code: a public proof of concept exists.
- Attacks: CERT-EU says none have been reported in the wild yet.
Rapid7’s demonstration needed about 128 GB of traffic and a specific server setup. That limits how easy it is. It does not make the flaw harmless.
Is a typical WordPress or small-business site affected?
It depends on your host’s stack, not on WordPress.
- Hosts running nginx with HTTP/2 on and an unpatched version: affected.
- Many shared and cPanel hosts run Apache or LiteSpeed instead of nginx. They are not affected by this flaw.
- Sites behind a CDN or proxy: the question moves to the server behind it. An origin server that accepts only HTTP/1.1 cannot be attacked through HTTP/2.
The fix
nginx open source 1.31.9 and 1.30.7, released November 18, fix it. NGINX Plus has fixes in 37.3.0.1 and 37.0.8.1. NGINX Plus R34 to R36 have no fix listed. A reload is not enough. nginx must be restarted or upgraded in place so the old program stops running.
If a host cannot patch right away, turning HTTP/2 off is a stopgap. Your host would do that, not you.
The same release also fixes a separate HTTP/2 use-after-free flaw (CVE-2026-123633) and a resolver flaw (CVE-2026-123634), among others.
What we checked for our clients
On November 18 we checked the servers that host our clients’ sites. None of them run nginx as the public web server.
We have one internal nginx container. It is not reachable from the internet and has HTTP/2 off. We are updating it anyway.
Ask your host
Send your host this one question:
Do you run nginx with HTTP/2 enabled on the servers behind my website, and if so, have they been updated to 1.31.9, 1.30.7 or a patched package?
A good host answers in a sentence. A vague answer tells you something too. Our website support and maintenance plans include this kind of check. For why your host belongs in your security plan, read your website host is now part of your security risk.
Sources
Jeremy Johnson
Owner
Jeremy co-owns Robben Media and directs strategy for every client engagement. With a Computer Engineering degree from Missouri S&T, he brings deep technical expertise in web development, SEO, and automation. Before acquiring Robben Media in 2023, Jeremy led marketing and branch management in the mortgage industry. He believes marketing should be measured by revenue generated, not impressions reported.