Skip to main content

Proof of concept is public. Updated

nginx2root checker: check, fix and mitigate

  • CVE-2026-123007
  • 4 more CVEs
  • CVSS 4.0 9.2

nginx2root is a set of five memory-safety flaws in NGINX. The worst one lets an unauthenticated attacker run commands on any server with HTTP/2 enabled, and it has been in every release since 1.9.5, from 2015. A separate Linux kernel bug then turns the NGINX worker into root.

Fixed in 1.30.7 (stable) and 1.31.9 (mainline). Older branches get no release. Some distributions have backported the fixes, others have not yet, and end-of-life ones never will. The GetPageSpeed repository has 1.30.7 for all of them, CentOS 7 included.

Install fixed NGINX 1.30.7

Sources: the nginx.org security advisories and the write-up by Xint, who found the flaws.

Is my NGINX vulnerable?

A free nginx2root checker that reads the package release, so it can tell a backported fix from an old version number. Add your configuration and it shows which of the five CVEs can reach you.

Any system: nginx -v
RHEL, CentOS, Alma, Rocky, Amazon: rpm -q nginx
Debian, Ubuntu: dpkg -l nginx
With per-CVE exposure: (nginx -V; nginx -T) 2>&1

Try an example:

The check runs in your browser. Nothing you paste is sent anywhere.

For a full review of the configuration, use the NGINX config checker: it also lists every other known CVE for your version.

Which NGINX versions are affected by nginx2root

Each of the five flaws is an attack path of its own: they do not need to be chained. What differs is the configuration that makes each one reachable. CVE-2026-123007 needs nothing but HTTP/2, which most HTTPS servers have on.

CVEFlawReachable whenAffectedFixed in
CVE-2026-123007 HTTP/2 flow control overflow Reachable on any listener with HTTP/2 enabled. 1.9.5 to 1.31.8 1.30.7, 1.31.9
CVE-2026-123633 HTTP/2 use-after-free Needs HTTP/2 and requests passed to an upstream (proxy_pass, fastcgi_pass and the like). 1.19.7 to 1.31.8 1.30.7, 1.31.9
CVE-2026-121810 HTTP/3 use-after-free Needs an HTTP/3 (QUIC) listener and requests passed to an upstream. 1.25.0 to 1.31.8 1.30.7, 1.31.9
CVE-2026-123634 Resolver use-after-free Needs a resolver, a proxy_pass target that contains a variable, and subrequests (mirror, SSI, auth_request). 0.6.18 to 1.31.8 1.30.7, 1.31.9
CVE-2026-113425 Mail proxy use-after-free Needs a mail {} block that proxies with auth_http. 0.5.33 to 1.31.8 1.30.7, 1.31.9

F5 scores CVE-2026-123007 at 8.1 under CVSS 3.1 and 9.2 under CVSS 4.0; nginx.org rates it "major". The version ranges above are the ones nginx.org publishes. NGINX 1.30.7 and 1.31.9 also fix five CVEs that are not part of nginx2root: the config checker lists every known CVE for a given version.

The version number is not enough. Distributions backport fixes and keep the version they shipped, so a fixed package can still print 1.20.1 or 1.24.0. And a patched package on disk does not mean a patched process: NGINX keeps running the old binary until it is restarted.

How to fix nginx2root on your platform

Installing a fixed build is the only complete fix. You do not have to wait for your distribution: NGINX 1.30.7 is in the GetPageSpeed repository today for every platform marked in the first column below. The second column is the distribution's own nginx package, as of November 19, 2026.

PlatformFrom GetPageSpeedFrom the distributionDetail
RHEL 8, 9 and 10 1.30.7 ready: install Not fixed yet nginx, and the nginx:1.24 and nginx:1.26 module streams. Listed as affected. No erratum yet. Red Hat CVE page
AlmaLinux 8, 9 and 10 1.30.7 ready: install Fixed nginx on 9 and 10 (1.20.1-32.el9_9.1.alma.4, 1.26.3-16.el10_3.1.alma.3) and the nginx:1.24 and nginx:1.26 streams. Backported in two steps on November 18. The older nginx:1.14 to nginx:1.22 streams have no fixed build in the repositories yet. ALSA-2026:A024
Rocky Linux 1.30.7 ready: install Not fixed yet nginx 1.26.3-16.el10_3.1 on Rocky Linux 10. No fixed build yet. Rocky Linux follows Red Hat's errata.
CentOS 7 1.30.7 ready: install No fix coming EPEL nginx 1.20.1-10.el7. End of life: EPEL 7 is frozen, and the nginx.org CentOS 7 repository stopped at 1.26.1.
Amazon Linux 2023 1.30.7 ready: install Fixed 1.30.7-1.amzn2023.0.1. All five CVEs. ALAS2023-2026-3494
Amazon Linux 2 (nginx1 extra) 1.30.7 ready: install Fixed 1.30.7-1.amzn2.0.1. All five CVEs. ALAS2NGINX1-2026-018
Ubuntu 22.04, 24.04 and 26.04 LTS 1.30.7 ready: install Fixed 1.18.0-6ubuntu14.23, 1.24.0-2ubuntu7.20, 1.28.3-2ubuntu1.13. All five CVEs, backported on November 19. USN-9159-1
Ubuntu 20.04 1.30.7 ready: install Ubuntu Pro only 1.18.0-0ubuntu1.7+esm5. Fixed for Ubuntu Pro subscribers only. Without Pro the package stays at the affected build. USN-9159-1
Ubuntu 16.04 and 18.04 Not built Ubuntu Pro only 1.10.3-0ubuntu0.16.04.5+esm11, 1.14.0-0ubuntu1.11+esm6. Fixed for Ubuntu Pro subscribers only. USN-9159-1
Debian 12 and 13 1.30.7 ready: install Not fixed yet nginx 1.22.1, 1.26.3. Listed as vulnerable. No DSA yet. Debian security tracker
Alpine 3.22 to 3.24 Not built Fixed 1.28.3-r8, 1.30.7-r0. All five CVEs, as a backport on 3.22 and 3.23. Alpine security tracker

Red Hat lists RHEL 8, 9 and 10 as affected and has published no erratum, and Rocky Linux follows Red Hat. AlmaLinux did not wait: on AlmaLinux 9 and 10, sudo dnf upgrade nginx brings nginx-1.20.1-32.el9_9.1.alma.4 or nginx-1.26.3-16.el10_3.1.alma.3, which carry the fixes as backports, and the nginx:1.24 and nginx:1.26 module streams on AlmaLinux 8 and 9 are fixed the same way. The first AlmaLinux builds of November 18 fixed only the two HTTP/2 flaws, so check which one you have: the checker above tells them apart. The older nginx:1.14 to nginx:1.22 streams have no fixed build in the repositories yet.

Everywhere else in this family, NGINX 1.30.7 from the GetPageSpeed repository replaces the distribution package in place:

sudo dnf -y install https://extras.getpagespeed.com/release-latest.rpm
sudo dnf -y upgrade nginx
sudo systemctl restart nginx
nginx -v

Tested on Rocky Linux 10 and AlmaLinux 8, 9 and 10: the upgrade replaces nginx, nginx-core and nginx-filesystem with one nginx package and the distribution's nginx-mod-* modules with their nginx-module-* counterparts. No module stream needs disabling, and nginx -t passes on the existing configuration. An edited nginx.conf is kept, with the packaged one saved beside it as nginx.conf.rpmnew. The restart matters: until it, the old process keeps serving. Free to install; commercial production use requires a subscription. Without one, a small license notice appears on HTML pages after 30 days.

Step by step, with the output to expect: nginx2root on RHEL, Rocky Linux, AlmaLinux and CentOS.

Check the running binary

The package manager replaces the file on disk. The process keeps the old one mapped until NGINX restarts, and nginx -v reads the file, not the process. Ask the kernel which binary the master runs:

sudo ls -l /proc/$(cat /run/nginx.pid)/exe

If the line ends with (deleted), the master still runs the old binary: restart NGINX. A plain nginx -s reload does not help, because it re-reads the configuration with the same binary. Workers shown as worker process is shutting down in ps are old ones finishing long connections, such as HTTP/2 streams or downloads; they exit by themselves, or at once with a restart.

Fixed NGINX 1.30.7 packages for every distribution

GetPageSpeed builds NGINX from the upstream sources for each distribution it supports, the end-of-life ones too. NGINX 1.30.7 and 1.31.9 were in the repository at 16:06 UTC on November 18, within the hour of the disclosure.

Distributions with fixed GetPageSpeed NGINX builds
DistributionReleasesNGINX
AlmaLinux / Rocky / RHEL 7, 8, 9, 10 1.30.7, 1.31.9
Fedora 44, 45 1.30.7, 1.31.9
Amazon Linux 2, 2023 1.30.7, 1.31.9
Ubuntu 20.04, 22.04, 24.04, 26.04 1.30.7, 1.31.9
Debian 12, 13 1.30.7, 1.31.9

RHEL, AlmaLinux, Rocky Linux, CentOS 7, Amazon Linux

sudo yum -y install https://extras.getpagespeed.com/release-latest.rpm
sudo yum -y upgrade nginx
sudo systemctl restart nginx

Ubuntu and Debian

curl -fsSLO https://extras.getpagespeed.com/release-latest.deb
sudo apt-get -y install ./release-latest.deb
sudo apt-get update
sudo apt-get -y -o Dpkg::Options::=--force-confold install nginx
sudo systemctl restart nginx

Free to install; commercial production use requires a subscription. Without one, a small license notice appears on HTML pages after 30 days.

  • The upstream release itself. 1.30.7 carries all ten security fixes of November 18, the five nginx2root ones among them.
  • Modules move with it. More than 140 dynamic modules, from Brotli to ModSecurity, were rebuilt for 1.30.7 and update in the same transaction, so nothing is left refusing to load.
  • Later updates do not drop connections. When one GetPageSpeed build replaces another, the package upgrades the running binary in place: a new master starts and the old workers finish their requests. Tested on Rocky Linux 10 from 1.28.2 to 1.30.7 with an HTTP/2 download in flight.
  • End-of-life systems included. CentOS 7 and Ubuntu 20.04 get the same 1.30.7 as current releases.
  • NGINX-MOD too. NGINX-MOD moved to 1.30.7 the same day; its Amazon Linux 2 build is in the early channel.

See subscription plans

Running many servers? GetPageSpeed Amplify shows the NGINX version on every monitored host and flags the ones with known CVEs.

Stopgaps until you can update

Each stopgap switches off the feature one flaw lives in. The vulnerable code stays in the binary, so these buy time and nothing more. Match them to what the checker found reachable.

Turn HTTP/2 off (CVE-2026-123007, CVE-2026-123633)

On NGINX 1.25.1 and newer, set http2 off; in every server block that shares the listening address and port, and remove any http2 parameter from the listen directives. On older versions, remove http2 from listen 443 ssl http2;. Clients fall back to HTTP/1.1; native gRPC stops working.

listen 443 ssl;
http2 off;
sudo nginx -t && sudo nginx -s reload
openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>&1 | grep -E 'ALPN protocol|No ALPN'

Tested on NGINX 1.30.7: with http2 on; the second command prints ALPN protocol: h2, and after the change it prints No ALPN negotiated. Behind a CDN or load balancer, run it against the NGINX server itself.

Remove the QUIC listeners (CVE-2026-121810)

Comment out every listen ... quic line, set http3 off;, and stop advertising HTTP/3:

listen 443 ssl;
# listen 443 quic reuseport;
http3 off;
add_header Alt-Svc 'clear' always;

After the reload, sudo ss -lunp 'sport = :443' must not show nginx.

Take DNS lookups out of the request path (CVE-2026-123634)

This one needs a resolver, a proxy_pass whose target contains a variable, such as proxy_pass http://$host;, and a subrequest. Xint tested it with mirror, and says other subrequest features such as SSI may reach it too. Point proxy_pass at a fixed upstream group, so no name is resolved while a request is handled:

upstream backend_fixed {
    server 10.0.0.10:8080;
}
location / {
    proxy_pass http://backend_fixed;
}

Keep strangers off the mail proxy (CVE-2026-113425)

Only servers with a mail {} block that proxies with auth_http are exposed. The flaw fires during login and needs no valid credentials. Bind the IMAP, POP3 and SMTP listeners to an internal address or limit them to trusted addresses in the firewall.

Close the old connections

A reload applies the new configuration to new connections only. HTTP/2 and mail sessions that were already open stay with the old workers and the old settings. If ps still shows workers that are shutting down, restart NGINX.

Block the kernel half: SCTP

The step from the NGINX worker to root uses the kernel's SCTP module, which is loaded on demand. On hosts that do not use SCTP, stop it from loading:

echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
lsmod | grep sctp    # no output: the module is not loaded

Tested on Rocky Linux 10: with the line in place modprobe sctp fails. It does not unload a module that is already loaded, and it does nothing for a kernel with SCTP built in.

A stopgap is not a patch. It closes the paths that are known today. Update NGINX, then restart it.

How nginx2root works

Four of the flaws are use-after-free bugs and one is an integer overflow. None needs a vulnerable application behind NGINX, and none needs a login.

The nginx2root chain Crafted HTTP/2 frames overflow a flow-control window, which leads to an out-of-bounds write and code running as the NGINX worker. A Linux kernel SCTP flaw then raises the worker to root. HTTP/2 frames no login needed Window overflow write past the buffer Code as the worker CVE-2026-123007 Root on the host kernel SCTP flaw Updating NGINX breaks the chain at the second box. Blocking SCTP breaks it at the last one.
From an anonymous HTTP/2 connection to root, as demonstrated by Xint.

CVE-2026-123007: HTTP/2 flow control overflow

HTTP/2 limits how much data a peer may send with flow-control windows, which the protocol caps at 31 bits. Xint found that NGINX lets a send window grow past that cap when queued credit is returned. A later check on the oversized value underflows, and NGINX ends up copying with an invalid length: reads and writes past the end of a heap buffer. The frames that drive this, WINDOW_UPDATE and RST_STREAM, are control frames, so the attack leaves nothing in the access log. The code has been there since HTTP/2 support arrived in 1.9.5.

CVE-2026-123633 and CVE-2026-121810: use-after-free under connection pressure

When NGINX runs out of worker_connections it reuses idle ones. With HTTP/2 (CVE-2026-123633) or HTTP/3 (CVE-2026-121810) and a request on its way to an upstream, that reuse can free a request that is still in use. An attacker creates the pressure by opening connections, so a generous worker_connections setting is not a defence.

CVE-2026-123634: use-after-free in the resolver

When a request and its subrequest wait for the same DNS answer, the resolver can free state that one of them still uses. It takes a resolver, a name resolved at request time, and a subrequest, which is why the tested setup combines a variable in proxy_pass with mirror.

CVE-2026-113425: use-after-free in the mail proxy

During login, the mail proxy asks an HTTP service whether the credentials are valid. A client that goes away at the right moment gets its session freed while the authentication request still points at it.

The kernel half: from the worker to root

NGINX workers run as an unprivileged user, so code execution there is not yet control of the host. Xint closed that gap with a use-after-free in the Linux kernel's SCTP send path, present since Linux 4.15. It worked from inside a Docker container as well, because containers share the host kernel. The kernel bug had no CVE id and no fix when this page was last updated, which is why the SCTP stopgap is worth applying even on a patched NGINX.

Detect nginx2root attacks

An attack through CVE-2026-123007 sends control frames, which NGINX does not log as requests, inside TLS. Look at what surrounds the requests instead. These checks follow Xint's guidance.

Programs started by an NGINX worker

A worker has no reason to start a shell. Find the worker's user id, then record every program it executes:

ps -eo uid,user,pid,args | grep '[n]ginx: worker process'
sudo auditctl -a always,exit -F arch=b64 -S execve,execveat -F euid=NGINX_UID -k nginx_worker_exec
sudo ausearch -k nginx_worker_exec -ts recent -i

The rule records only what happens after you add it, so an empty result does not clear the past.

Workers that crash

A failed attempt can kill a worker:

sudo grep -Ei 'worker process.*exited on signal|signal 11' /var/log/nginx/error.log | tail -n 20
sudo coredumpctl list nginx

Connections that receive much and log little

The tested attack keeps one connection open for minutes and floods it with WINDOW_UPDATE frames, while opening many short TLS connections from the same address:

sudo ss -tinp state established '( sport = :443 )'

Run it twice, a little apart. A peer whose bytes_received climbs fast while NGINX sends little back, with no upload to explain it, deserves a block and a closer look. Logging $connection, $connection_requests and $request_length lets you compare what a connection received with what it logged.

None of these is proof alone, and clean logs do not prove a host is safe. A program started by a worker is the clearest sign: if you find one, treat the host as compromised, rotate its credentials and rebuild it.

nginx2root timeline

  1. Xint finds the flaws.
  2. Xint reports them to F5 through HackerOne.
  3. Xint finishes validating the patches from the NGINX team.
  4. NGINX 1.30.7 and 1.31.9 are released with ten security fixes, and Xint publishes its write-up. GetPageSpeed publishes both versions for every supported distribution at 16:06 UTC, and NGINX-MOD 1.30.7 two hours later. AlmaLinux ships backports for AlmaLinux 9 and 10 the same day. A public proof of concept appears.
  5. Ubuntu publishes USN-9159-1 with backports for 22.04 to 26.04, and for 16.04 to 20.04 under Ubuntu Pro. Amazon's advisories for Amazon Linux 2023 and the Amazon Linux 2 nginx1 extra are out. Red Hat and Debian still list their packages as affected.
  6. This page last updated.

Need hands-on help?

A fleet you cannot update by hand, an old platform, or a server you suspect was reached? GetPageSpeed engineers update, harden and monitor production NGINX servers.

See Server Care

nginx2root FAQ

What is nginx2root?

nginx2root is the name Xint gave to five memory-safety flaws in NGINX disclosed on November 18, 2026, plus a Linux kernel bug that turns them into a root compromise. The lead flaw, CVE-2026-123007, lets an unauthenticated attacker run commands as the NGINX worker process on a server with HTTP/2 enabled. The other four are CVE-2026-123633 (HTTP/2), CVE-2026-121810 (HTTP/3), CVE-2026-123634 (resolver) and CVE-2026-113425 (mail proxy).

Which NGINX versions are affected by nginx2root?

CVE-2026-123007 affects every NGINX release from 1.9.5, the first one with HTTP/2, to 1.31.8. The fixes are in NGINX 1.30.7 (stable) and 1.31.9 (mainline). Older branches such as 1.28, 1.26 and 1.24 get no upstream release, so they are protected only by a vendor backport or by moving to 1.30.7.

Am I affected if HTTP/2 is turned off?

Not by the two HTTP/2 flaws, CVE-2026-123007 and CVE-2026-123633. The other three do not need HTTP/2: CVE-2026-121810 needs an HTTP/3 listener with an upstream, CVE-2026-123634 needs a resolver with a variable in proxy_pass, and CVE-2026-113425 needs a mail proxy with auth_http. Paste your configuration into the checker on this page to see which ones it can reach.

Does disabling HTTP/2 fix nginx2root?

It blocks two of the five CVEs and fixes none. Setting http2 off (or removing http2 from the listen directives on NGINX older than 1.25.1) closes CVE-2026-123007 and CVE-2026-123633 until you can update. The vulnerable code stays in the binary, and native gRPC stops working without HTTP/2. Update to a fixed build.

Why does nginx -v still show an old version after my distribution patched it?

Distributions backport security fixes into the version they already ship. AlmaLinux 9, for example, fixed nginx2root in nginx-1.20.1-32.el9_9.1.alma.4, and nginx -v on that build still prints 1.20.1. Compare the full package version from rpm -q nginx or dpkg -l nginx instead: the checker on this page does that.

Is the nginx package of Ubuntu or Debian fixed?

Ubuntu fixed all five CVEs on November 19, 2026 in USN-9159-1: nginx 1.18.0-6ubuntu14.23 on 22.04, 1.24.0-2ubuntu7.20 on 24.04 and 1.28.3-2ubuntu1.13 on 26.04. Ubuntu 16.04, 18.04 and 20.04 are out of standard support and get the fix through Ubuntu Pro only. Debian lists 12 and 13 as vulnerable, with no advisory as of November 19, 2026. These are backports, so nginx -v keeps printing the old version: compare the package version from dpkg -l nginx. NGINX 1.30.7 for Ubuntu 20.04 to 26.04 and Debian 12 and 13 is in the GetPageSpeed repository.

Is there an nginx2root fix for CentOS 7?

Not from the usual sources. CentOS 7 is end of life, the EPEL nginx 1.20.1 package is frozen, and the nginx.org CentOS 7 repository stopped at 1.26.1. The GetPageSpeed repository still builds NGINX for CentOS 7 and has 1.30.7: yum install https://extras.getpagespeed.com/release-latest.rpm, then yum upgrade nginx and restart NGINX.

Will NGINX 1.28, 1.26 or 1.24 get a fix?

No. NGINX maintains one stable and one mainline branch, and only 1.30.7 and 1.31.9 carry the fixes. nginx.org published no patches for older branches. If you run one of them from a distribution, wait for that distribution's backport or switch to a 1.30.7 package.

Is nginx -s reload enough after updating?

No. A reload re-reads the configuration with the binary that is already running. The new binary starts serving only after a restart or an in-place binary upgrade. GetPageSpeed packages perform that upgrade themselves when one GetPageSpeed build replaces another: the new master starts and the old workers finish their connections. Coming from a distribution package, restart NGINX once. Then check that /proc/$(cat /run/nginx.pid)/exe does not end with "(deleted)".

Is nginx2root being exploited in the wild?

There was no confirmed exploitation as of November 19, 2026, and none of the five CVEs was in the CISA Known Exploited Vulnerabilities catalog on November 18. A public proof of concept for CVE-2026-123007 exists, and Xint demonstrated working exploits against servers on AWS, Google Cloud and Azure, so treat that as a matter of time.

What is the "root" part of nginx2root?

The NGINX flaws give an attacker the privileges of the worker process, usually an unprivileged user. Xint chained them with a separate, still unpatched use-after-free in the Linux kernel's SCTP code, present since Linux 4.15, to become root, also from inside a Docker container. The kernel bug has no CVE id or fix yet. Hosts that do not use SCTP can block the module with "install sctp /bin/false" in a file under /etc/modprobe.d/.

Are OpenResty, Angie, Tengine and freenginx affected?

They are built on the NGINX code that carries these flaws, and as of November 19, 2026 none of them had published a fixed release or a statement. The latest OpenResty is based on NGINX 1.31.8, which is affected. Apply the configuration stopgaps and watch each project's security page.

Is the Kubernetes ingress-nginx controller affected?

The community ingress-nginx project was archived in March 2026 and has published no release for these CVEs, so its bundled NGINX stays vulnerable. HTTP/2 is normally enabled on an ingress, which makes CVE-2026-123007 reachable. Turn HTTP/2 off in the controller configuration as a stopgap and plan a move to a maintained controller.

Is nginx2shell the same as nginx2root?

Yes. Some reports call the same five CVEs NGINX2Shell, by analogy with PHP2Shell. Xint, who found them, uses the name nginx2root.

Do my dynamic modules need an update too?

Yes. A dynamic module is built for one exact NGINX version and will not load into another, so moving to 1.30.7 means every module must be rebuilt for 1.30.7 as well. The GetPageSpeed repository rebuilds its modules for each NGINX release, and they update in the same transaction as NGINX.

Is NGINX Plus affected?

Yes. F5 lists NGINX Plus as vulnerable to the same flaws and names 37.3.0.1 and 37.0.8.1 as the fixed builds. See F5's advisories for your release.

Is there a free nginx2root checker?

Yes, the checker at the top of this page is free and needs no signup. Paste the output of nginx -v, rpm -q nginx or dpkg -l nginx and it tells a backported fix from an old version number. Add the output of nginx -T and it shows which of the five CVEs your configuration can reach. Everything runs in your browser.

References