F5 has released patches for NGINX2Root, five critical flaws in NGINX that allow unauthenticated remote code execution and already have public exploits. Any company running a website, online shop, API or reverse proxy on NGINX is affected, Docker included. Update to 1.30.7 or 1.31.9 today and fully restart the service.
The essentials
- The five flaws are CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634. All score 9.2 on CVSS 4.0, according to SecurityWeek.
- The most serious, CVE-2026-123007 ("nginx2root"), affects servers with HTTP/2 and has been in the code since version 1.9.5, released on 22 September 2015 (The Hacker News).
- Every NGINX Open Source version from 1.9.5 to 1.31.8 is vulnerable. NGINX Plus is affected too.
- Fixed versions: Open Source 1.31.9 (mainline) and 1.30.7 (stable); NGINX Plus 37.3.0.1 and 37.0.8.1. No fix is listed for NGINX Plus R34 to R36.
- Rapid7 and Censys have published proofs of concept. As of 18 November there were no known attacks in progress and the flaw was not in CISA's KEV catalogue.
Am I affected if I don't even know whether I use NGINX?
Quite possibly. NGINX sits behind many websites, online shops, APIs and reverse proxies, and many hosting plans, control panels and containers ship with it without anyone noticing. Censys estimates around 9 million NGINX services with an affected version and HTTP/2 enabled, plus another 103 million that don't reveal their version, as reported by The Hacker News.
Each flaw needs specific conditions. CVE-2026-123007 and CVE-2026-123633 require HTTP/2 enabled. CVE-2026-121810 requires HTTP/3. CVE-2026-113425 requires NGINX acting as a mail proxy. CVE-2026-123634 requires a specific server name configuration with variables and SSI or mirror. If your server accepts HTTP/2, you are exposed to the most serious flaw.
If you use Docker, pay attention: Xint chained the flaw with a Linux kernel bug (SCTP) to escape a container and gain root on the host.
Is it serious if there are no attacks yet?
F5 says code execution is only possible with ASLR disabled or bypassed. Wiz claims the flaws themselves allow ASLR to be bypassed, and Rapid7's public exploit gets around it by leaking memory addresses. That exploit needs about 128 GB of HTTP/2 traffic, but Censys says it reproduced the behaviour over cleartext HTTP/2 without that volume (SecurityWeek).
In practice, the technical barrier is lower than the vendor advisory suggests. With public exploits out, scanning is likely to start soon.
Can I wait for my distribution's package?
As of 18 November, Ubuntu and Debian had not yet released fixed packages. The official NGINX Docker images already had the 1.31.9 and 1.30.7 tags. Until the package arrives, CIRCL's guidance suggests disabling HTTP/2: it blocks CVE-2026-123007 and CVE-2026-123633, but not the other three flaws.
What to do today
- Ask your IT person or hosting provider for an inventory of where NGINX runs: servers, containers and appliances.
- Update to 1.30.7 or 1.31.9, or to the fixed NGINX Plus versions (37.3.0.1 or 37.0.8.1).
- Fully restart NGINX. A simple
reloadleaves the old binary running. - If your distribution doesn't have the package yet, disable HTTP/2 (
http2 off) and check withopenssl s_client -alpn h2that the server no longer accepts it. This does not cover HTTP/3 or the mail proxy. - If you sit behind a CDN, check the origin server too.
- Look in the logs for unusual processes spawned by NGINX workers and unusual outbound connections.
- If you use a managed service, demand written confirmation from your provider that it has been patched.
What it means for a small business
The hard part here isn't the patch, it's knowing where to apply it. Small businesses rarely install NGINX on purpose: it comes inside the hosting plan, the shop's control panel, a Docker image someone set up a while ago, or an appliance. That's why the inventory comes first. And that's why written confirmation from your provider matters: it's how "it's done" stops being an assumption.
Don't get stuck on the ASLR debate. There are public exploits, a researcher who has already broken out of a container onto the host, and millions of exposed servers. No confirmed attacks is a window, not a guarantee.
Be careful with the workaround too: disabling HTTP/2 closes two of the five flaws. It buys time; it doesn't settle the matter. And the full restart is the step most easily forgotten: updating without restarting leaves you where you started. If nobody on your side can do the inventory and verify the restarts this week, lean on a cybersecurity service to do it with you.
Frequently asked questions
Is a reload enough after updating?
No. A reload leaves the old binary running. You need to fully restart NGINX.
Am I protected if I disable HTTP/2?
Only against CVE-2026-123007 and CVE-2026-123633. It doesn't cover the HTTP/3 flaw, the mail proxy flaw, or the configuration flaw involving variables and SSI or mirror.
Am I safe if my website sits behind a CDN?
Not necessarily. You also need to check the origin server.