85

nginx2root: AI finds holes faster than servers get patched

In short

  1. nginx2root is five flaws in nginx, fixed on 18 November 2026 in nginx 1.31.9 and 1.30.7. The worst, CVE-2026-123007, lets an attacker run code on a server with HTTP/2 turned on, without a password.
  2. The bug has been in nginx since 2015. Most of the five were found with AI-driven analysis, and a working exploit for the main flaw went public on the day of the fix.
  3. Update nginx and restart it fully, because a reload keeps the old program running. If you cannot update today, turn off HTTP/2 for now.

On 18 November 2026, nginx released versions 1.31.9 and 1.30.7 with fixes for ten flaws. Five of them are known together as nginx2root. The worst one lets an attacker run code on a web server without logging in.

The bug sat in nginx for ten years. This time it was found with the help of AI, and attack code appeared on GitHub the same day the fix came out.

What happened

The main flaw, CVE-2026-123007, is a memory corruption bug in how nginx handles HTTP/2 flow control. An attacker who can reach an HTTP/2 port can run code on the server with the rights of the nginx worker process. No password is needed.

F5, the company behind nginx, rates it 9.2 out of 10 under CVSS 4.0. The Cloud Security Alliance gives the same score to all five nginx2root flaws:

  • CVE-2026-123007: memory corruption in HTTP/2 flow control;
  • CVE-2026-123633: use-after-free in HTTP/2;
  • CVE-2026-123634: use-after-free in the DNS resolver;
  • CVE-2026-121810: use-after-free in HTTP/3;
  • CVE-2026-113425: use-after-free in the mail proxy.

On its own the main flaw gives the rights of the nginx worker, not full control of the machine. In tests, researchers at Xint went further and reached root by chaining it with an unpatched Linux kernel bug in SCTP.

Why AI is part of this story

The main flaw has been in every release since version 1.9.5, which came out in September 2015. For ten years nobody caught it, in one of the most widely used programs on the internet.

According to Xint, one of its researchers found that flaw by hand. Its automated, AI-driven scan then found the other four without human guidance. The nginx changelog credits the second HTTP/2 flaw to a researcher from Vexera AI. The Cloud Security Alliance titled its research note “AI-Found HTTP/2 RCE”.

Holes in nginx itself are being found more often. Xint counts 26 entries in the nginx security advisory list in 2026 up to 17 November, not counting nginx2root, against two in all of 2025. The Cloud Security Alliance notes that not all of that growth comes from AI tools.

Attack code moved just as fast. By the time the fix was out, Rapid7 had published a working exploit for the main flaw on GitHub. Ubuntu and Debian did not yet have fixed packages that day.

As of 19 November, no attacks in the wild had been reported. With working code public, that can change any day.

This is the new pace. AI makes searching old code for holes cheap and fast, and a public fix now comes with public attack code. A server that gets updates once a quarter stays open for weeks.

Is your server affected

nginx serves 29.7% of websites whose web server is known, according to W3Techs in November 2026. It also often sits in front of APIs, admin panels and app backends, so it may run on your servers even if your website does not use it.

For the main flaw, every open-source nginx from 1.9.5 through 1.31.8 is affected if HTTP/2 is turned on. The fixed versions:

  • nginx 1.31.9 (mainline) and 1.30.7 (stable). Older branches get no separate fix and need to move to one of these;
  • NGINX Plus 37.0.8.1 and 37.3.0.1;
  • F5 NGINX Ingress Controller 5.8.0. The community ingress-nginx project was archived in March 2026 and gets no more fixes.

To check the version, run nginx -v on the server. A Linux distribution can ship the fix without changing that number, so also check its security notices.

To see from outside whether a site accepts HTTP/2, run openssl s_client -connect yoursite.com:443 -alpn h2. The line “ALPN protocol: h2” means it does.

Not sure what runs on your servers? Let us check and fix it for you.

Send us your site or server address. We check the nginx version and settings, update it, restart it safely and tell you what we found.

Help me check my server

What to do today

  1. Update nginx to 1.31.9 or 1.30.7, or install the fixed package from your Linux distribution as soon as it is out.
  2. Restart nginx fully after the update. A reload applies settings but keeps the old program running.
  3. Cannot update today? Turn off HTTP/2 on every listener: http2 off; on nginx 1.25.1 and newer, or remove http2 from the listen line on older versions. This closes only the two HTTP/2 flaws, and services that need HTTP/2, such as gRPC, stop working.
  4. Turn off HTTP/3 and the mail proxy if you do not use them.
  5. Rebuild Docker images that ship nginx, and check the ingress controller in Kubernetes.
  6. If you do not use SCTP, block the kernel module that researchers used to reach root: add install sctp /bin/false to a file in /etc/modprobe.d/.

Let us keep your servers patched

nginx2root will not be the last one. In October it was PHP2Shell, two critical holes in PHP. Now it is nginx. AI tools go through old code faster every month, and every find starts a clock for whoever runs the server.

When a critical vulnerability comes out, we check your servers, install the fixes and confirm the hole is closed. After that we keep them up to date, so the next critical fix goes in before it can be used against you.

Let us keep your servers updated.

Send us your site or server address. We check it today and tell you what needs fixing.

Help me with my servers

FAQ

What is nginx2root?

nginx2root is the name for five flaws in the nginx web server, fixed on 18 November 2026 in versions 1.31.9 and 1.30.7. The worst, CVE-2026-123007, lets an attacker run code on a server with HTTP/2 turned on, without a login.

Is my server affected?

If it runs open-source nginx from 1.9.5 through 1.31.8 with HTTP/2 turned on, yes. NGINX Plus is affected too and is fixed in 37.0.8.1 and 37.3.0.1. Older branches have no separate fix: move to 1.30.7 or 1.31.9.

Is a reload enough after the update?

No. A reload applies the new settings but keeps the old program running. Restart nginx fully, or use its live binary upgrade.

Can I just turn off HTTP/2?

Only for a few days. It closes the two HTTP/2 flaws, not the other three, and services that need HTTP/2, such as gRPC, stop working. An update is the only full fix.

Has anyone been attacked yet?

As of 19 November 2026, no attacks in the wild had been reported. A working exploit for the main flaw is already public, so that can change any day.

Did AI really find these flaws?

Partly. Xint says one of its researchers found the main flaw by hand, and its automated, AI-driven scan found the other four. The nginx changelog also credits a researcher from Vexera AI for the second HTTP/2 flaw.

Sources

Rate this article
0 reviews
Comments
Be the first to
Rate this article
0 reviews
Comments
Be the first to

Recommended articles