Inter-office memo

To
Everyone running nginx
From
Mo, Chief Executive
Date
November 19, 2026, 6:14 AM CST
Re
nginx2root

nginx2root: AI helped find critical nginx flaws. Who’s at risk, and which versions fix it

On November 18, 2026, nginx 1.31.9 and 1.30.7 fixed nginx2root, five flaws that can let attackers run code on nginx servers without logging in, found partly with AI. The worst, CVE-2026-123007, needs only HTTP/2 on; a public exploit exists, but no attacks had been reported by November 19. Patched distro packages keep their old version numbers, and turning HTTP/2 off blocks the two HTTP/2 flaws until you update.

What nginx fixed on November 18

On November 18, 2026, the nginx project released nginx 1.31.9, its mainline version, and 1.30.7, its stable one, with fixes for ten vulnerabilities. Five of them can let an attacker run code on the server without logging in. Xint, one of the teams that reported them, calls those five and a Linux kernel bug it chains them with nginx2root.

They don’t all need the same setup. Here is each one, with the versions nginx’s advisories list and the conditions from Xint’s write-up:

CVE Where the bug is What it needs Affected Blocked by turning off HTTP/2
CVE-2026-123007 HTTP/2 flow control HTTP/2 on 1.9.5 to 1.31.8 Yes
CVE-2026-123633 HTTP/2 connections HTTP/2 on, requests proxied to a backend 1.19.7 to 1.31.8 Yes
CVE-2026-121810 HTTP/3 connections HTTP/3 on, requests proxied to a backend 1.25.0 to 1.31.8 No
CVE-2026-123634 The DNS resolver resolver, a proxy_pass built from the request, and mirror or another subrequest 0.6.18 to 1.31.8 No
CVE-2026-113425 The mail proxy A mail proxy with proxy on and auth_http 0.5.33 to 1.31.8 No

The 1.30 line before 1.30.7 is affected too. The other five fixes cover a denial of service over TLS 1.3, a crash with PROXY protocol version 2, a buffer overflow with alias and try_files, a client certificate bypass in the stream module and a validation flaw in ssl_preread.

The ratings differ. nginx’s own page calls CVE-2026-123007 “major” and CVE-2026-123633 “medium.” F5, which owns nginx and assigned the CVEs, scores all five 8.1 out of 10 under CVSS 3.1 and 9.2 under CVSS 4.0 in its CVE records. Red Hat rates CVE-2026-123007 Critical, and Ubuntu gives it High priority because “this is an RCE.”

Who’s at risk

Anyone with HTTP/2 on, for CVE-2026-123007. The bug has been there since nginx added HTTP/2 in 1.9.5, in 2015. Wiz “demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.” Code runs with the nginx worker process’s permissions.

It isn’t a quick attack. Rapid7, whose researcher Stephen Fewer built a working exploit, says it takes “approximately 128 GB of HTTP/2 data”: about two minutes over a 10 Gbit/s link and seventeen over 1 Gbit/s. “Due to nginx’s default one hour connection lifetime, a network slower than approximately 300 Mbit/s will take over the one hour connection limit threshold and will not be able to succeed.” Its method also depends on a memory-copy routine glibc picks on x86-64 processors with AVX-512, though “Alternative RCE exploitation strategies may be viable, but none are currently known.” A CDN or proxy in front of nginx may get in the way, since the attacker’s frames “will likely not be retransmitted” exactly, but that only helps if nginx can’t be reached directly.

Proxies running low on connections, for CVE-2026-123633. F5’s record says it needs HTTP/2 for clients, requests proxied to a backend, and a worker “running low on worker_connections.”

Particular setups, for the other three: HTTP/3 in front of a backend, a resolver with a variable proxy_pass and mirrored requests, or nginx as a mail proxy.

That’s a lot of servers. In a Shodan snapshot of November 10, Xint found 98.9% of 11.94 million nginx hosts that report a version running one in CVE-2026-123007’s range, which it calls “a measure of version prevalence, not a count of exploitable endpoints.”

The host itself, with a second bug. Xint chained CVE-2026-123007 with a flaw in the Linux kernel’s SCTP code to get root, and “the chain also escaped a Docker container running nginx and obtained root on the underlying host.” That kernel bug had no CVE or patch on November 18, as Tenable notes, and Xint is keeping most of its details private.

How AI found it

Five teams found the two HTTP/2 bugs independently, Wiz says: Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint. At least three of them used AI.

Xint, from the security firm Theori, found all five. A researcher testing a new capability pointed it at “a slice of nginx, about 50,000 lines,” and “Ninety minutes later it flagged high severity issues with reproduction steps specific enough to become a working exploit in under ten minutes,” its site says. It credits the worst bug to the person: “The human researcher was the one that found the specific vuln that affects a default nginx setup with HTTP/2 enabled.” Xint built what it learned into the tool, which “then found the other 4 critical nginx vulnerabilities with no human guidance.” It doesn’t say which models it runs.

Wiz, now part of Google Cloud, found both HTTP/2 bugs with Atlas, “the harness powering Wiz’s AI Code scanning solution,” and its researchers “used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate the impact.” Its conclusion: “The flaws were already there; AI helped us find them.”

Ikotas Labs appears in F5’s credits for CVE-2026-123007 as “(@ikotas00 using GPT-6 Astra).” Rapid7 doesn’t say whether Fewer used AI.

This is the third such disclosure in a month, after PHP2Shell and Java4Shell the day before. Xint counts how fast nginx’s list is growing: two new vulnerabilities in 2025, and 26 this year by November 17, before these ten. “Complexity can no longer be relied upon as a barrier to discovery or exploitation,” Wiz writes.

Is it being exploited?

Not that anyone has reported. On November 18, CERT-EU wrote that “no exploitation in the wild has been reported yet,” and CISA’s Known Exploited Vulnerabilities catalog released that day doesn’t list any of the five. CISA’s assessment in CVE-2026-123007’s record reads exploitation “none,” automatable “no,” technical impact “total.”

Unlike Java4Shell’s finders, Rapid7 published its exploit. Its repository, public since November 18, has a short script that triggers the bug and a full exploit, which “is only suitable to demonstrate the given RCE exploitation strategy against a local freshly started Docker container” and “will likely fail against a vulnerable NGINX server which has multiple concurrent clients.” Wiz and Xint have kept theirs private. Wiz expects “a shorter window between disclosure and exploitation” as AI speeds up this kind of research.

Which versions fix it

Where your nginx comes from decides which update you need. Here is where each source stood on November 19:

Where your nginx comes from Fixed in Status on November 19
nginx.org 1.31.9 mainline, 1.30.7 stable Released November 18
NGINX Plus 37.3.0.1 and 37.0.8.1 Released; R33 to R36 get no fix
Docker’s official image nginx:1.31.9 and nginx:1.30.7 latest and mainline point to 1.31.9, stable to 1.30.7
Ubuntu USN-9159-1 Released November 19
Amazon Linux 2023 ALAS2023-2026-3494 Released November 18
Debian 12 and 13 Not yet Still listed as vulnerable
Red Hat Enterprise Linux 8, 9 and 10 Not yet Listed as “Affected,” no update
OpenResty Not yet 1.31.8.1, based on nginx 1.31.8, is the newest
Kubernetes ingress-nginx No upstream fix Retired in March 2026

Distro packages keep their old numbers. Ubuntu’s fixed packages are 1.30.4-7ubuntu1.2 on 26.10, 1.28.3-2ubuntu1.13 on 26.04, 1.24.0-2ubuntu7.20 on 24.04, 1.18.0-6ubuntu14.23 on 22.04, and 1.18.0-0ubuntu1.7+esm5 on 20.04 through Ubuntu Pro, which also has fixes for 18.04 and, with its Legacy add-on, 16.04. Each still reports its old nginx version, so “Confirm patch status from the relevant vendor advisory instead of relying on nginx -v alone,” as Xint puts it. Debian’s tracker shows bookworm and trixie vulnerable and only unstable fixed, in 1.30.6-4. Red Hat has no errata yet and suggests turning HTTP/2 off. Amazon Linux also fixed the nginx1 extra for Amazon Linux 2 on November 19.

NGINX Plus releases R33 to R36 have no patch, Tenable reads F5’s advisory, so “those customers need to move to a 37.x release.”

Containers need rebuilding. Docker’s official nginx tags for 1.31.9 and 1.30.7 were published on November 18 and 19, but an image built on an older tag keeps its old nginx until you rebuild and redeploy it.

OpenResty hasn’t shipped. Its downloads page still offers 1.31.8.1, and an issue opened on November 18 asks for an update.

Kubernetes’ ingress-nginx gets no fix. The repository was archived on March 24, 2026, and is “now read-only.” Chainguard’s fork, which bundles nginx 1.27.1, merged a backport of the CVE-2026-123007 fix on November 18. An issue on AKS’s app routing add-on says its image ships nginx 1.27.1 with “HTTP/2 is enabled on the 443 listener by default,” and asks Microsoft for a patched image and a supported way to turn HTTP/2 off. F5’s own NGINX Ingress Controller is a separate project.

What to do

  1. Find every nginx you run. That means servers and the containers, ingress controllers and OpenResty builds that bundle their own. “Distribution packages, appliances, and container images may backport a security fix while retaining an older version string,” Xint warns.

  2. Check whether HTTP/2 is on and reachable. Xint’s checks are nginx -v 2>&1 for the version, nginx -V 2>&1 | grep -q -- '--with-http_v2_module' && echo 'HTTP2_MODULE=present' || echo 'HTTP2_MODULE=absent' for the module, and, from outside your network:

    openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/null 2>&1 \
      | grep -E 'ALPN protocol:|No ALPN negotiated|Connection refused|connect:errno|handshake failure'

    “ALPN protocol: h2” means the server accepts HTTP/2. If a CDN sits in front, run it against nginx directly too.

  3. Update, then restart. Install 1.31.9 or 1.30.7, or your vendor’s fixed package, and restart nginx: “A configuration reload alone does not replace the running executable,” Xint says.

  4. Where you can’t update yet, turn HTTP/2 off. On nginx 1.25.1 or later, set http2 off; in each affected server block and remove http2 from its listen directives; on older versions, change listen 443 ssl http2; to listen 443 ssl;. Run sudo nginx -t and reload, then repeat the openssl check. Clients fall back to HTTP/1.1, but “services that require HTTP/2, such as native gRPC, will be affected.” This blocks CVE-2026-123007 and CVE-2026-123633 only. For HTTP/3, remove the quic listeners and set http3 off; for the resolver bug, point proxy_pass at a fixed upstream; for the mail proxy, Tenable suggests binding it to loopback or firewalling it.

  5. Block SCTP where you don’t use it. Until the kernel is fixed, Xint suggests putting install sctp /bin/false in a .conf file under /etc/modprobe.d/. It “does not unload a module that is already loaded, and it does not disable SCTP compiled into the kernel.”

  6. Look for signs. Worker crashes show up with sudo grep -Ei 'worker process.*exited|signal 11|segfault' /var/log/nginx/error.log, though CERT-EU says that’s “not a high-fidelity indicator” of a successful attack. The clearest sign is a program started by an nginx worker, which Xint’s write-up shows how to catch with an auditd rule. The attack’s frames aren’t logged as requests, so access logs may show nothing.

Checking your servers with an agent

Steps 1 and 2 are tedious across many machines, and a coding agent such as Claude Code or Codex running where it can reach your servers can do them. Keep it read-only, and keep it away from Rapid7’s exploit. A prompt along these lines works:

Check whether the nginx installs you can reach are affected by nginx2root (CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425), fixed in nginx 1.31.9 and 1.30.7. Read only: don't edit configuration, restart services or run any exploit. For each host, container image and ingress controller, record the nginx version and, for distro packages, the full package version, and compare it with the distribution's security advisory. Note whether the binary has --with-http_v2_module, whether the running configuration turns on http2, http3 or quic, uses resolver with a variable proxy_pass alongside mirror, or runs the mail proxy, and whether the server answers h2 from outside. Return a table, and list what you couldn't check.

Check what it reports against the table above before acting on it, and make the updates and restarts yourself.

What hasn’t been said

  • Whether anyone is exploiting it. No one had reported attacks by November 19, but the exploit is public.
  • When the rest of the fixes ship. Debian, Red Hat, OpenResty and AKS’s app routing add-on had given no dates.
  • What the kernel bug is. Xint’s SCTP flaw has no CVE and no patch, and its details are private until there is one.
  • Which models found what. Xint doesn’t name the models its scan runs, Rapid7 doesn’t say whether AI was involved in its find, and the credits differ: nginx’s changelog thanks only Xint.io for CVE-2026-123007, while F5’s record thanks four teams.
  • Whether F5’s cloud services are affected. F5 is still evaluating them, CyberScoop reports, while BIG-IP and F5OS aren’t vulnerable.

We’ll update this memo when Debian and Red Hat ship their fixes, when OpenResty releases one, or if attacks are reported.

9.Questions.

Am I affected by nginx2root?

Most likely, if your nginx is older than 1.31.9 or 1.30.7, has no backported fix from your vendor, and has HTTP/2 turned on. That’s all CVE-2026-123007 needs, and Wiz ran code on an nginx serving nothing but static files. The other four flaws need particular setups, such as HTTP/3 or the mail proxy, and nginx 1.9.4 and older, which predate HTTP/2, aren’t affected by the worst one.

Which nginx version fixes nginx2root?

nginx 1.31.9 (mainline) and 1.30.7 (stable), released November 18, 2026, and NGINX Plus 37.3.0.1 and 37.0.8.1. Distributions patch their own packages without changing the version nginx reports, such as Ubuntu 24.04’s fixed 1.24.0-2ubuntu7.20. After updating, restart nginx, because a reload doesn’t replace the running program.

Does turning off HTTP/2 protect me?

From two of the five flaws, CVE-2026-123007 and CVE-2026-123633, yes. Set `http2 off;` in each affected server block on nginx 1.25.1 or later, or remove `http2` from its `listen` lines on older versions. It doesn’t touch the HTTP/3, resolver and mail proxy flaws, which have their own stopgaps.

Is nginx2root being exploited?

No attacks had been reported by November 19, 2026, and CISA’s list of exploited vulnerabilities doesn’t include it. But Rapid7 published a working exploit for CVE-2026-123007 on disclosure day, so anyone can study one.

Was nginx2root found by AI?

Mostly. Xint says a researcher found CVE-2026-123007 and its automated scan then found the other four “with no human guidance,” and Wiz found both HTTP/2 flaws with its AI system Atlas. F5 credits one other finder as “using GPT-6 Astra.”

My server says nginx 1.24.0. Is it vulnerable?

Not necessarily. Ubuntu and Debian fix their packages without changing nginx’s version number, so compare the full package version with your distribution’s advisory. On November 19, Ubuntu’s fixes were out, while Debian 12 and 13 and Red Hat Enterprise Linux were still waiting for theirs.

Enjoy Agentic Industries · Checked against its sources on