NGINX2Root security guide: 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, Plus 37.0.8.1 and 37.3.0.1. Update nginx, restart workers, verify the package, and check for compromise.

NGINX2Root: Check Your Web Servers and Patch Today

Posted by:

|

On:

NGINX2Root – TL;DR

On November 18, 2026, nginx shipped fixes for five flaws that let an attacker with no password run code as the nginx worker. Researchers call the set NGINX2Root. The widest one, CVE-2026-123007, has been in every official release since HTTP/2 arrived in 2015, and it only needs HTTP/2 turned on. A separate Linux kernel bug in SCTP, still unpatched and with no CVE number, can turn that worker access into root on the host, including from a container. CERT-EU and Tenable had seen no attacks in the wild as of November 18. A public proof of concept for CVE-2026-123007 exists anyway, so treat internet-facing nginx as a today problem.

  • Update nginx to 1.31.9 (mainline) or 1.30.7 (stable), or install your distro’s fixed package. NGINX Plus moves to 37.0.8.1 or 37.3.0.1. Releases R33 through R36 have no patch and need that upgrade.
  • Restart the workers. A reload keeps the old program in memory, and connections that were already open stay on the old workers.
  • Verify the package, not the short version string. Ubuntu and Debian often keep printing 1.18.0 or 1.24.0 after a security update.
  • If you cannot update today, turn HTTP/2 off on listeners an attacker can reach. That blocks two of the five flaws. It leaves the HTTP/3, resolver, and mail-proxy flaws in place.
  • On Linux hosts that do not use SCTP, stop the kernel from loading that module until a kernel fix exists. A vulnerable nginx box is not automatically root on the host. The lab chain used this path.

This guide covers what shipped, who is exposed, a 30-minute check, how to update, and how to tell whether anyone got in before you patched. Feel free to share it. The vendor picture will keep moving, and the Updates section is where that lands.

In this guide

What is NGINX2Root?

NGINX2Root is the name Xint gave to five memory bugs in nginx, plus a separate Linux kernel bug they chained to those bugs in the lab. F5 and nginx.org do not use the nickname. The five nginx bugs were fixed on November 18 in open source 1.31.9 and 1.30.7. Each one can run code with the privileges of the nginx worker, which is usually an ordinary account such as nginx or www-data, not root.

The five flaws

Tenable reports F5’s CVSS v4 score as 9.2 for each of the five. nginx.org uses its own scale and marks two of them major and three medium. CERT-EU lists 8.1. The action is the same at every one of those numbers: install the fixed build and restart.

CVEWhat has to be truenginx.orgVulnerable releases
CVE-2026-123007HTTP/2 is enabled on a port an attacker can reach. A static-file site is enough.major1.9.5–1.31.8
CVE-2026-123633HTTP/2, the request is forwarded to a backend, and the worker is short of connections.medium1.19.7–1.31.8
CVE-2026-121810HTTP/3, the request is forwarded to a backend, and the worker is short of connections.medium1.25.0–1.31.8
CVE-2026-123634A resolver is set, proxy_pass builds a name from the request, and a subrequest resolves that same name.medium0.6.18–1.31.8
CVE-2026-113425nginx is a mail proxy with proxy on and auth_http. The attacker needs no mailbox password.major0.5.33–1.31.8

The version ranges are nginx.org’s. Xint’s tested path for the resolver bug used mirror with mirror_request_body off, and they warn that other subrequests, including SSI, can reach the same bug. Turning mirror off is not a fix. Their tested mail path starts slightly earlier than the range nginx.org publishes. Where the two differ, patch to 1.31.9 or 1.30.7 anyway.

What the researchers showed

Three details decide how fast you move:

  • Code execution has been shown. nginx’s own note for CVE-2026-123007 says a worker can crash, “or might have potential other impact.” Xint and Wiz both went further and ran code. Wiz did it against a server hosting ordinary static files over HTTP/2 with TLS. Censys reproduced the memory corruption in four of the five in a lab and did not reach code execution (BleepingComputer).
  • A public proof of concept exists, and it is constrained. Tenable says a Rapid7 researcher published one for CVE-2026-123007 on November 18. It targets a particular 64-bit Linux build, has to learn memory addresses as it goes, and needs on the order of 128 gigabytes of HTTP/2 traffic. Tenable also says it is a poor fit for a server behind a proxy that terminates HTTP/2, or for a connection too slow to finish inside nginx’s one-hour limit. Do not download exploit repositories onto a server you care about. Plenty of lookalikes will be malware, the same lesson as PHP2Shell.
  • Nobody had reported attacks in the wild yet. CERT-EU said that on November 18, and Tenable said the same and noted that none of the five was in CISA’s Known Exploited Vulnerabilities catalog. Several teams found the HTTP/2 bugs independently, so assume working exploit code will spread past the people who already have it.

The path to root is a different bug

The “to root” half of the nickname is not an nginx CVE. Xint chained a worker compromise with a use-after-free in the Linux kernel’s SCTP code, introduced in Linux 4.15 in 2018. In their tests the chain escaped a Docker container running nginx and got root on the host. As of November 18 that kernel bug had no CVE and no fix, and the researchers were withholding the details until a patch exists (Tenable, Sysdig).

A host that never uses SCTP can still be exposed. On most distributions the module is not loaded until some program opens an SCTP socket, and then the kernel loads it. Sysdig’s lab opened one socket from the nginx worker inside the official nginx:1.31.8 image, and the host loaded sctp. Containers share the host kernel, so a container escape here is a host compromise. A vulnerable nginx by itself does not mean the attacker is root. They also need a reachable SCTP path, or some other way up.

Timeline

Xint’s dates are in UTC. The release is the GitHub tag, not the date they had scheduled.

DateWhat happenedSource
Oct 11Xint finds the vulnerabilities while preparing for ZeroDay Cloud 2026. One researcher found CVE-2026-123007. An automated scan found the other four.Xint
Oct 16Reported to F5 through HackerOne.Xint
Oct 20HackerOne finishes validation.Xint
Oct 27Reports reach nginx’s developers.Xint
Nov 9–10nginx asks Xint to check the patch. Xint finishes that check on Nov 10. The vulnerable code was still on the master branch that day.Xint
Nov 18Open source 1.31.9 is tagged at 15:54 UTC. Stable 1.30.7 ships the same day. F5’s advisory is K000164058. CERT-EU publishes advisory 2026-022 at 17:30 UTC.nginx, CERT-EU
Nov 18Tenable reports a public proof of concept for CVE-2026-123007, and no exploitation in the wild. The five CVEs are not in CISA’s catalog.Tenable
Nov 19BleepingComputer reports Censys figures: about 8.8 million services potentially exposed to CVE-2026-123007 by version and HTTP/2, more than 511,000 already patched or mitigated, and about 104 million nginx services that do not show a version.BleepingComputer

The same release fixes five more bugs that are not part of the NGINX2Root nickname. The one to know is CVE-2026-118899, an infinite loop while reading a request body over TLS 1.3. nginx.org rates it major, and Tenable lists F5’s CVSS v4 score as 8.7. It is a denial of service, not the code-execution set. One of the other four, CVE-2026-120993, is mainline only: nginx.org lists it in 1.31.4 through 1.31.8 and fixed in 1.31.9, with no 1.30.7 line, because that code was never on the stable branch. The full list is on nginx.org.

Are you affected by NGINX2Root?

You are in scope if anything you operate speaks HTTP with an nginx binary you have not confirmed as fixed. That includes a reverse proxy in front of an app, a container image, a Kubernetes ingress that vendors its own nginx, OpenResty, a control panel, and a mail proxy. Managed hosting is your host’s job. A VPS, a Docker host, and an appliance you update yourself are yours.

  • HTTP/2 on a reachable port is the broad path, CVE-2026-123007. Modern configs turn it on with http2 on or with http2 on the listen line. A site that only serves files is included.
  • A proxy to a backend adds CVE-2026-123633 when the listener is HTTP/2, and CVE-2026-121810 when it is HTTP/3. Both show up when the worker runs out of connection slots.
  • Request-time DNS is CVE-2026-123634: a resolver directive, a proxy_pass that contains a variable such as the host from the request, and a subrequest. Mirror is the setup Xint exploited. It is not the only one.
  • A mail proxy with proxy on and auth_http is CVE-2026-113425. IMAP, POP3, and SMTP listeners count. A plain web server with no mail block is clear of this one.
  • NGINX Plus R33 through R36, and the 37.x builds before the fixed releases, are in Tenable’s affected list. The builds that close the set are 37.0.8.1 and 37.3.0.1. Tenable says CVE-2026-123633 is also fixed in 37.0.7.1 and 37.2.0.1, and CERT-EU still lists those two as affected, so they are not a place to stop.

The version string is a weak signal

The version string is a weak signal. Xint notes that Ubuntu 24.04 ships nginx 1.24.0, Ubuntu 22.04 ships 1.18.0, and Debian 12 ships 1.22.1, and that earlier security updates on Ubuntu 22.04 kept printing 1.18.0 while the package revision climbed. A November backport can do the same. Read the distro advisory and the full package version. An official release at 1.31.9 or 1.30.7 is fixed. Anything from 1.9.5 through 1.31.8 still contains the HTTP/2 flow-control bug until a vendor says that build includes the fix.

What the internet counts leave out

Internet-wide counts are easy to overread. On November 10, Xint’s Shodan search saw 56.7 million nginx hosts, 11.94 million of them with a recognizable version, and 98.9% of those versions inside 1.9.5–1.31.8. That does not mean 98.9% are exploitable: HTTP/2 has to be on, and a backport would still show the old version. BleepingComputer quotes Censys, as of November 19, at about 8.8 million services potentially exposed to CVE-2026-123007 once HTTP/2 is taken into account, with more than 511,000 already patched or mitigated. Another 104 million nginx services do not disclose a version at all. Florian Roth, quoted in the same piece, found HTTP/2 on about two-thirds of a few hundred sampled HTTPS endpoints and warned that version-only exposure claims mislead.

How to check your servers in 30 minutes

Work through this once per machine, image, and appliance. Write down the package string or image tag, not just “nginx is installed.”

1. Find every binary

Host packages, container images, a Kubernetes ingress, a control panel, and any mail proxy. The nginx in front of an app and the nginx inside a container are two systems.

2. Read the version, then the package

nginx -v prints a string such as nginx/1.31.8. 1.31.9 and 1.30.7 are the fixed open source releases. 1.9.5 through 1.31.8 is the vulnerable range for CVE-2026-123007. 1.9.4 and earlier never had HTTP/2. If the string is a distro version, open the changelog or the security advisory and look for these five CVE ids. The short version can stay the same when the fix lands.

3. See whether HTTP/2 is actually on

The build info should include --with-http_v2_module. The running config should be searched for http2 on and for http2 on a listen line, after comments are ignored. No hits means this binary is not on the CVE-2026-123007 path. A config you edited and did not reload is not the config that is running.

4. Check from outside

A TLS handshake that negotiates h2 means HTTP/2 is offered to the internet. If Cloudflare or another proxy sits in front, that test sees the proxy. Repeat it against the origin, from a network that can reach the origin.

5. Note the narrower paths

A listen line containing quic, or http3 on, is the HTTP/3 bug. A resolver plus a proxy_pass that contains a variable is the resolver bug, especially with mirror or SSI. A mail block with proxy on and auth_http is the mail bug.

6. On Linux, look at SCTP

A module that is already loaded stays loaded until reboot. A modprobe rule will not turn SCTP off when it is built into the kernel. When nothing you run needs SCTP, plan to block the module from loading. Telecom signaling and some Kubernetes network plugins do need it, so check before you block it.

How to fix NGINX2Root

  1. Update. Open source: 1.31.9 on mainline, 1.30.7 on stable, or the distro package whose advisory names these CVEs. NGINX Plus: 37.0.8.1 or 37.3.0.1. R33 through R36 do not get a patch. Rebuild container images. Pulling a new package on the host does nothing for the nginx inside an image.
  2. Restart, don’t reload. A configuration reload does not replace the running executable. Workers that are shutting down keep the connections they already had, and they keep the old code. Restart nginx through the service manager, or use nginx’s binary upgrade if that is how you already ship releases. Expect a short break for downloads and mail sessions that were in progress.
  3. Verify the package. Confirm the full package version or image tag, and confirm the worker processes started after the install. Then repeat the outside HTTP/2 check only if you intended to leave HTTP/2 on. Leaving it on is fine once the fixed binary is the one running.

Stopgaps if you can’t patch today

Turn HTTP/2 off: on 1.25.1 and later, set http2 off and remove http2 from listen. On older releases, remove http2 from listen. That covers CVE-2026-123007 and CVE-2026-123633 only. Services that require HTTP/2, including gRPC, will break, so treat this as a temporary outage you chose. HTTP/3 needs the quic listeners removed, http3 off, and an end to advertising HTTP/3. The resolver bug needs proxy_pass pointed at a fixed upstream instead of a name taken from the request. Bind the mail proxy to localhost, or allow only trusted addresses at the firewall.

Block SCTP where you do not need it

A modprobe rule that refuses to load sctp stopped the kernel path in Sysdig’s lab. It does not unload a module that is already loaded, and it does nothing if SCTP is compiled into the kernel. Reboot after the rule if the module is loaded. Skip this on hosts that actually use SCTP.

Address randomization still matters, and it is not a substitute for the patch. The published exploit has to learn memory addresses from the server as it goes. Keep randomization on, and remove any setup that turns it off.

Were you already hit?

Patching does not remove an attacker who got in first. No official indicators of compromise have been published. Look for behavior. CERT-EU’s compromise note is the right bar: a crashed worker is a hint of an attempt, and it is not proof of code execution.

  • A program started by a worker is the strong sign. A normal worker does not launch a shell. Match the parent process to nginx before you call it a breach, because other services may share the same account.
  • Workers dying in the error log. Look for a worker process that exited on a signal, including signal 11. One crash has ordinary causes. Several, from the same outside address, in the same hour, deserve a closer look.
  • A loud connection that barely shows up as requests. Xint’s HTTP/2 attack keeps one connection open and sends a large volume inward while the server sends little back, alongside many short connections from the same address. The frames that trigger CVE-2026-123007 are not written as ordinary requests, so the access log can look quiet while the connection counters climb.

Any one of those, with a normal explanation, can be nothing. Two of them together, with no upload or client you recognize, is when you cut the source off and start an incident. There is no public evidence yet that this has happened at large. The check is still worth the half hour on any server that was on the internet unpatched after November 18.

Lessons for small teams

  • The bug waited eleven years. CVE-2026-123007 arrived with HTTP/2 in nginx 1.9.5, in 2015. “We run a recent nginx” was not a defense. 1.31.8 was still vulnerable.
  • The version string is the wrong artifact. Distro backports keep the old number. Record the package revision and the image digest. When the next advisory lands, that list is the whole job.
  • Automated research is shortening the quiet period. Xint says a researcher found the first bug and a scan found the other four without a person guiding it. PHP2Shell, disclosed in October, came with the same kind of gap between a patch and working exploits. Plan on days, not weeks.
  • A container is not a second kernel. Patching the nginx image and blocking SCTP on the host are two changes. The image update does not close the kernel path, and the kernel workaround does not close HTTP/2.

NGINX2Root FAQ

Does updating WordPress, the app, or the WAF fix this?

No. The bugs are in nginx. A current application on an old proxy is still exposed. A WAF in front may stop some exploit traffic, and it is not the fix. Install the fixed nginx and restart it.

Is turning HTTP/2 off enough?

It blocks CVE-2026-123007 and CVE-2026-123633. It does not block the HTTP/3, resolver, or mail-proxy bugs, and it breaks clients that require HTTP/2, including gRPC. Turn it back on after the fixed binary is running.

Which version do I install?

Open source mainline: 1.31.9. Open source stable: 1.30.7. A distro package is fine when its advisory names the five CVEs, even if nginx -v still prints the old number. NGINX Plus: 37.0.8.1 or 37.3.0.1. Tenable says CVE-2026-123633 is also fixed in 37.0.7.1 and 37.2.0.1. CERT-EU still lists those builds as affected, so move on to 37.0.8.1 or 37.3.0.1.

Is the kernel bug fixed?

Not as of the November 18 reports. It has no CVE id yet. Until a kernel update says otherwise, block the SCTP module on hosts that do not use it, and reboot if it is already loaded.

Are attackers using this?

CERT-EU and Tenable said no on November 18, and the CVEs were not in CISA’s catalog. A proof of concept for CVE-2026-123007 was already public the same day. Check servers that were exposed. Ignore repositories offering a “nginx2root exploit” or a scanner, and do not run them.

What about OpenResty, ingress controllers, and appliances?

They ship their own nginx. Ask the vendor which build contains these five fixes, and apply that build. The version string inside the product is not enough, for the same reason a distro package is not enough.

Updates

  • November 19, 2026: First version, the day after nginx 1.31.9 and 1.30.7 shipped. Checked against nginx.org, the 1.31.9 changelog, CERT-EU 2026-022, Xint, Tenable, Sysdig, and BleepingComputer.

Running PHP on these same boxes? The PHP2Shell guide is the matching check for the runtime under WordPress and everything else you serve.

Sources