ELS Status for nginx2root and the November 18 nginx Release
TuxCare is backporting fixes for the November 18 nginx CVEs, including CVE-2026-123007, to the nginx packages on supported end-of-life distributions, covering each CVE that applies to a given build. The work is in progress, and patched packages will arrive through the same repositories and package manager commands you already use.
Status per distribution and CVE will show up in the TuxCare CVE Tracker as each package ships.
Key Takeaways
- nginx2root pairs five nginx code execution bugs with a kernel flaw that turns worker access into root.
- The worst one, an HTTP/2 flaw, dates back to 2015 and is fixed in 1.30.7 and 1.31.9.
- Ten nginx CVEs were fixed upstream on November 18, but most major distributions hadn’t shipped packages yet.
- nginx builds on end-of-life distributions fall inside the affected ranges for four to seven CVEs.
The Short Version
What happened. On November 18, 2026, nginx released 1.30.7 (stable) and 1.31.9 (mainline) with fixes for ten CVEs. Five of them belong to nginx2root, the name Xint gave a chain of six bugs. Each of the five nginx bugs leads to remote code execution on its own, and the sixth, a Linux kernel bug in SCTP, turns that foothold into root on the host. Jump to this section →
Who’s affected. Anyone running nginx with HTTP/2 enabled on an unpatched build older than 1.30.7 (stable) or 1.31.9 (mainline), all the way back to 1.9.5, is exposed to CVE-2026-123007, the most widely reachable bug. The other four need specific setups: HTTP/2 or HTTP/3 in front of a backend, request-time DNS lookups with mirror, or the mail proxy with proxy on and auth_http. Jump to this section →
How bad it is. Researchers at Xint, Rapid7 and Wiz each demonstrated code execution without credentials, and Rapid7 has published a proof of concept. That exploit works under lab conditions and needs roughly 128 GB of traffic, and no attacks had been reported as of November 18. Jump to this section →
Where things stand. Upstream fixes are out. Ubuntu, Debian and Red Hat list their nginx packages as vulnerable with no update yet. For end-of-life distributions that no longer get vendor updates, TuxCare’s backported nginx patches are out for all but Debian 10, which is close behind. Jump to this section →
What to do today. Run the checks below to find servers with HTTP/2 enabled. Where you can’t upgrade to 1.30.7 or 1.31.9 today, turn HTTP/2 off on exposed listeners and apply the configuration stopgaps for the other bugs. Then validate with nginx -t and restart nginx instead of reloading it. A restart briefly drops open connections, but a reload leaves old workers running. Jump to this section →
The Long Version
nginx is one of the most widely deployed web servers and reverse proxies in the world, and unauthenticated remote code execution bugs in it have been rare. CVE-2013-2028, a stack buffer overflow from more than a decade ago, is the usual example people reach for. On November 18, 2026, five arrived at once.
Xint, the research firm behind the nginx2root name, published a detailed write-up the same day nginx shipped its fixes. Rapid7 and Wiz published their own research on the HTTP/2 bugs, and reporting on the release says several teams found overlapping issues independently. nginx’s changelog credits Xint for CVE-2026-123007.
Upstream, the fix is a version upgrade. The hard part is everywhere nginx doesn’t come from nginx.org: distribution packages that keep an old version number and backport fixes, appliances, containers built months ago, and end-of-life systems whose vendors have stopped shipping updates. That’s where most of the work sits this week.
Five Bugs Behind One Name
The five nginx bugs in nginx2root are independent. Each one is enough for code execution with the privileges of the nginx worker process, and each needs a different configuration to reach.
| CVE | What it needs | Affected upstream versions | Blocked by turning off HTTP/2? |
| CVE-2026-123007 | HTTP/2 enabled | 1.9.5 to 1.31.8 | Yes |
| CVE-2026-123633 | HTTP/2 with requests proxied to a backend | 1.19.7 to 1.31.8 | Yes |
| CVE-2026-121810 | HTTP/3 with requests proxied to a backend | 1.25.0 to 1.31.8 | No |
| CVE-2026-123634 | Request-time DNS resolution in a request that also spawns a subrequest, such as mirror |
0.6.18 to 1.31.8 | No |
| CVE-2026-113425 | Mail proxy using proxy on with auth_http |
0.5.33 to 1.31.8 | No |
The ranges come from nginx’s advisory, and 1.30.7 on the stable branch is fixed even though it sits inside them numerically. Xint’s write-up lists different first versions for the resolver and mail bugs (1.13.4 and 0.5.15). Where the two disagree, the tables here follow nginx’s advisory.
CVE-2026-123007 is an accounting error in HTTP/2 flow control. When a client cancels streams that still have response data queued, nginx refunds that data’s credit to the connection’s send window without checking the protocol’s upper limit. A client that first tops the window back up with a WINDOW_UPDATE frame gets the same credit added twice, pushing the window past its maximum.
From there, an unsigned underflow lets later updates set the window to almost any value, and that value eventually becomes a bogus length in a memory copy on the TLS send path. Xint and Rapid7 both turned that copy into an address leak plus a heap overwrite, then into command execution.
CVE-2026-123007 needs no backend. A server handing out static files over TLS with HTTP/2 on is enough.
CVE-2026-123633 and CVE-2026-121810 are use-after-free bugs in connection reuse. When a worker runs short of connection slots, nginx closes idle connections to make room. Both bugs let an active HTTP/2 or HTTP/3 connection end up on that “safe to close” list, so the request’s own attempt to connect upstream can free the request it belongs to.
CVE-2026-123634 is a use-after-free in the resolver. When a main request and its subrequest wait on the same DNS answer, terminating the main request can free the subrequest’s resolver context while the resolver loop still points at it. Xint reached it through mirror, and both Xint and F5 point to SSI as another way in.
CVE-2026-113425 is a use-after-free in the mail proxy, reachable when it runs with proxy on and auth_http. If the client connection dies during an authentication lookup, the client’s session is freed while the connection to the authentication service still uses it. No valid credentials are needed.
The Other Five CVEs in the Same Release
The November 18 release also fixed five bugs outside nginx2root. They get less attention, but some of them reach further back than the headline bug.
| CVE | Issue | nginx severity | Affected upstream versions |
| CVE-2026-118899 | Infinite loop while reading a client request body over TLS 1.3 | Major | 1.13.0 to 1.31.8 |
| CVE-2026-120967 | SNI bypass with client certificate validation in the stream module | Medium | 1.25.5 to 1.31.8 |
| CVE-2026-125283 | Buffer overflow when using alias with try_files |
Minor | 0.9.6 to 1.31.8 |
| CVE-2026-123640 | Insufficient validation in the stream ssl_preread module |
Minor | 1.15.2 to 1.31.8 |
| CVE-2026-120993 | NULL pointer dereference with PROXY protocol version 2 | Minor | 1.31.4 to 1.31.8 only |
CVE-2026-118899 is a denial of service, not code execution, and nginx still rates it major. A worker stuck in that loop keeps burning CPU instead of serving requests. The alias and try_files overflow is rated minor, yet it reaches back to 0.9.6, so it applies to almost every nginx build still in service. The 1.30.7 stable release carries nine of the ten fixes. CVE-2026-120993 only exists in mainline, so it is fixed in 1.31.9 alone.
Who Is Actually Exposed
Version alone doesn’t decide exposure. Three things have to line up for CVE-2026-123007. The server runs an unpatched build (1.9.5 through 1.30.6, or 1.31.0 through 1.31.8), the binary includes the HTTP/2 module, and HTTP/2 is turned on in the configuration. The official Docker image and Ubuntu’s package both include the module. Stock configurations generally don’t switch HTTP/2 on, but plenty of HTTPS sites do.
Xint counted 56.7 million hosts on Shodan identifying as nginx as of November 10. About one in five reported a version, and 98.9% of those fell in the range affected by CVE-2026-123007. Those numbers say nothing about whether HTTP/2 is on or a backport is in place, so they describe the size of the haystack, not the count of vulnerable servers.
The other four nginx2root bugs narrow things down. CVE-2026-123633 needs HTTP/2 plus a backend, which describes most reverse proxy setups. CVE-2026-121810 needs HTTP/3, which only exists in 1.25.0 and later. The resolver bug (CVE-2026-123634) needs proxy_pass with a variable destination resolved through nginx’s own resolver while a subrequest waits on the same name. The mail bug (CVE-2026-113425) needs nginx acting as an IMAP, POP3 or SMTP proxy with proxy on and auth_http.
Version numbers can also mislead in the other direction. Ubuntu 22.04 still reports nginx 1.18.0 after years of security updates, because distributions backport fixes instead of moving to new upstream releases. The full package version, checked against your vendor’s advisory, tells you whether a fix is in. The output of nginx -v doesn’t.
How Hard This Is to Pull Off
There is a working public exploit. Rapid7 released proof-of-concept code on GitHub for CVE-2026-123007 that achieves unauthenticated code execution against a vulnerable 1.31.8 Docker image. It comes with real limits. Rapid7 says the published exploit is meant for a freshly started container with a clean heap, will likely fail against a busy server, and needs roughly 128 GB of HTTP/2 traffic over one connection. That’s about two minutes on a 10 Gbit/s link and about 17 minutes at 1 Gbit/s, and on links slower than about 300 Mbit/s, the default one-hour connection lifetime (keepalive_time) cuts it off. Builds older than 1.19.10 don’t have that cap. Rapid7 also expects an HTTP/2 proxy in front of nginx to break the exploit, because the attacker’s frames won’t pass through unchanged.
F5 notes that code execution depends on ASLR being disabled or bypassed. Every working exploit described so far bypasses it, using the bug itself to leak addresses. Xint says its HTTP/2 exploit worked under concurrent normal traffic, across hardware, and over public IP addresses on AWS, GCP and Azure. It hasn’t released that code.
The kernel half of the chain raises the stakes. Code execution as the nginx worker is a limited foothold, but Xint paired it with a use-after-free in the Linux kernel’s SCTP code to get root on the host, including from inside a Docker container. Xint says that bug has been in the kernel since v4.15 in 2018, and it’s withholding most details until a kernel fix exists. Updating nginx does nothing for this bug, so it needs tracking on its own. On many distributions the SCTP module loads automatically the first time a program opens an SCTP socket.
As of November 18, neither F5 nor the researchers had reported attacks in the wild, and CISA’s Known Exploited Vulnerabilities catalog didn’t list the CVE. Public code and a well-documented mechanism lower the bar for anyone who wants to try, so that can change.
Why the Scores Disagree
nginx’s own advisory rates CVE-2026-123007 and CVE-2026-113425 major and the other three nginx2root bugs medium. F5’s advisories score all five at 8.1 under CVSS 3.1 and 9.2 (Critical) under CVSS 4.0. Red Hat rates CVE-2026-123007 Critical, Ubuntu gives it High priority, and Xint calls all five critical.
Part of the spread is method. nginx uses its own labels, CVSS runs a formula, and each distribution scores against the packages it ships. The rest is attack complexity. The bugs need specific configurations, heavy traffic or heap grooming, which pulls nginx’s ratings down. The outcome when an attack succeeds is code execution on an internet-facing server, which pulls everyone else’s up. For patch planning, the configuration matters more than the label. An HTTP/2-enabled server on the internet belongs at the top of the patch list, whatever the score says.
Which Distributions Have a Fix
On release day, the upstream fix was the only one available for most systems. Here is where the main platforms stood on November 18, 2026, for CVE-2026-123007.
| Platform | Status for CVE-2026-123007 on November 18, 2026 |
| nginx.org 1.30.7 and 1.31.9 | Fixed |
| NGINX Plus | Fixed in 37.0.8.1 and 37.3.0.1, with no fix listed for R34 to R36 |
| Ubuntu 16.04 to 26.04 LTS | Vulnerable, fix needed, rated High priority |
| Debian 12, 13, testing and unstable | Vulnerable, no fixed package yet |
| RHEL 8, 9 and 10 | Affected, rated Critical, no errata yet |
| Alpine | 1.30.7-r0 published to the edge branch on November 18, so check your release branch |
| Amazon Linux and SUSE | No fixed package reported |
Check your vendor’s tracker before acting on this table, since packages can land within hours. The Ubuntu CVE page and the Debian security tracker both list per-release status, and Alpine’s package index shows what each branch carries.
What the Ten CVEs Mean for Older nginx Builds
End-of-life distributions ship old nginx versions, and being old doesn’t put them out of range. The table below maps the default nginx build on common end-of-life distributions against the upstream affected ranges for all ten CVEs. HTTP/3, the stream SNI bug and the PROXY protocol bug all arrived after these versions, so they drop out. Everything else stays.
| Distribution | nginx version | CVEs in the upstream affected range |
| CentOS 6, Oracle Linux 6, Ubuntu 16.04 | 1.10.3 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-125283 |
| CentOS 8, CentOS Stream 8 (default stream) | 1.14.1 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-118899 CVE-2026-125283 |
| Ubuntu 18.04 | 1.14.0 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-118899 CVE-2026-125283 |
| Debian 10 | 1.14.2 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-118899 CVE-2026-125283 |
| Debian 11, Ubuntu 20.04 | 1.18.0 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-118899 CVE-2026-125283 CVE-2026-123640 |
| CentOS 7, RHEL 7, Oracle Linux 7 (EPEL build) | 1.20.1 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-118899 CVE-2026-125283 CVE-2026-123640 CVE-2026-123633 |
| Alpine Linux 3.18 | 1.24.0 | CVE-2026-123007
CVE-2026-113425 CVE-2026-123634 CVE-2026-118899 CVE-2026-125283 CVE-2026-123640 CVE-2026-123633 |
The ranges come from nginx’s advisory, and a given distribution build can differ because of earlier backports, so treat this as a starting point. The practical takeaway holds either way. Every version in the table sits inside the affected range for CVE-2026-123007, and none of them will ever see an upstream nginx release that fixes it, because upstream no longer maintains 1.10 through 1.24. Short of replacing nginx with a newer build, a backport is the only way these versions get fixed.
Stopgaps Until You Can Patch
The real fix is 1.30.7, 1.31.9 or a vendor package with the backported fix. If that can’t happen today, match the stopgap to your configuration.
If HTTP/2 is on and the server faces the internet, turn HTTP/2 off. That blocks CVE-2026-123007 and CVE-2026-123633. Clients fall back to HTTP/1.1, though anything that needs HTTP/2, such as native gRPC, will break. On nginx 1.25.1 and later, set http2 off; in each affected server block and remove any http2 parameter from listen lines. On older builds, including every end-of-life distribution build in the table above, the http2 directive doesn’t exist, so remove http2 from the listen line instead:
listen 443 ssl;
Check every server block that shares the same address and port, since one block with http2 left in can keep it enabled for the whole listener. Run sudo nginx -t after editing so a typo doesn’t take the site down on restart.
If you resolve upstream names per request and use mirror, point proxy_pass at a fixed upstream group. That removes the request-time DNS lookup behind CVE-2026-123634. Setting mirror_request_body on stopped Xint’s exploit, but it doesn’t fix the bug, so don’t rely on it. If you copy Xint’s example for keeping mirroring, fix one line first. It defines backend_main_hotfix but points the main location’s proxy_pass at backend_hotfix, which doesn’t exist, so change it to backend_main_hotfix.
If you run HTTP/3, remove the quic listeners and set http3 off; to block CVE-2026-121810. Replace any Alt-Svc header that advertises HTTP/3 with add_header Alt-Svc 'clear' always; so clients stop trying HTTP/3.
If you run the mail proxy with proxy on and auth_http, keep untrusted clients away from it. Bind the IMAP, POP3 and SMTP listeners to loopback if nothing remote needs them, or restrict them by source address at the firewall. That is the only stopgap for CVE-2026-113425.
If the host doesn’t use SCTP, block the module. Placing install sctp /bin/false in a .conf file under /etc/modprobe.d/, such as /etc/modprobe.d/disable-sctp.conf, stops the module from loading through modprobe. It doesn’t unload a module already loaded, and it doesn’t help when SCTP is built into the kernel.
Two traps catch people after the change. A reload applies the new configuration only to new connections, so long-lived HTTP/2 and mail sessions keep running on old workers until a restart. And after installing a fixed package, a reload doesn’t replace the running binary either. Restart nginx through your service manager, or complete a live binary upgrade. A restart drops every open connection, so expect a short blip.
Checking a Server in a Few Minutes
Five commands cover the main questions on a single server:
nginx -v
nginx -V 2>&1 | grep -o -- '--with-http_v2_module'
sudo nginx -T 2>&1 | sed 's/#.*//' | grep -nE 'listen[[:space:]].*http2|^[[:space:]]*http2[[:space:]]+on[[:space:]]*;'
rpm -q nginx 2>/dev/null || dpkg -l 'nginx*' 2>/dev/null | grep '^ii'
openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>&1 | grep 'ALPN protocol'
The first line shows the upstream version. Anything from 1.9.5 to 1.30.6, or 1.31.0 to 1.31.8, needs a closer look. If the second command prints nothing, the binary has no HTTP/2 module and CVE-2026-123007 doesn’t apply. The third line strips comments and shows any directive that turns HTTP/2 on, so check which server block each match belongs to. Note that nginx -T reads the files, not the running configuration. The fourth line gives the full package version to compare against your vendor’s advisory (on Alpine, use apk info -v nginx). On RPM systems, rpm -q --changelog nginx | grep CVE-2026-123007 shows whether the package changelog mentions the fix, and if it doesn’t, the vendor advisory has the final word. Run the last line from outside your network with your own host name in both places. ALPN protocol: h2 means the endpoint you reached accepts HTTP/2 from the internet. If a CDN or load balancer sits in front, test the nginx host directly as well.
For the SCTP side of the chain, lsmod | grep sctp shows whether the module is loaded right now. Empty output doesn’t mean SCTP is unavailable, since the module can load on demand or be built into the kernel. For a fleet, run the same lines through whatever already handles your ad hoc commands, whether that’s Ansible, Salt or plain ssh in a loop.
Where ELS Stands
TuxCare’s engineers are backporting fixes into the nginx packages TuxCare maintains for end-of-life distributions. That covers every November 18 CVE that applies to a given build, not just the five nginx2root bugs. The work spans CentOS 6, 7 and 8, CentOS Stream 8, Oracle Linux 6 and 7, RHEL 7, Debian 10 and 11, Ubuntu 16.04, 18.04 and 20.04, and Alpine Linux 3.18. As of November 18, patched packages are out for all of them except Debian 10, which is finishing release testing.
They arrive through the repositories already configured on covered hosts, so the usual yum update nginx, apt upgrade nginx or apk upgrade nginx picks them up, followed by an nginx restart. The TuxCare CVE Tracker shows per-distribution status. Until a host has the update and a restart, the stopgaps above still apply, and the listen line edit is the one that matters for HTTP/2 on these older builds.
Get Endless Lifecycle Support →
Old nginx Doesn’t Stay Quiet
Ten years of review missed CVE-2026-123007, and once a researcher found it, an automated scan turned up four more within days.
That pace is the real story of 2026 for nginx. Xint counts 26 nginx advisories this year before nginx2root, against two in all of 2025, and it points to AI-assisted research finding bugs faster than ever. Code that looked settled is being reread by tools that don’t get tired, and each finding lands on every older version that still carries the same code.
Maintained branches got their fixes on disclosure day, and supported distributions will ship theirs on their own schedules. End-of-life builds get neither from the usual sources – no upstream release and no vendor package. A CentOS 7 or Ubuntu 18.04 web server still running its distribution’s nginx has the same HTTP/2 bug as a fresh 1.31.8 install, and nothing upstream will ever patch it. The same gap shows up in application dependencies, which is the problem SecureChain addresses for open source libraries.
So find the servers with HTTP/2 on, turn it off where a fixed package isn’t available yet, restart rather than reload, and make sure your end-of-life systems have a source of backported fixes before the next batch arrives.
Get Endless Lifecycle Support →
Timeline
| Date | Event |
| September 22, 2015 | nginx 1.9.5 adds HTTP/2 support, introducing the code behind CVE-2026-123007 |
| October 11, 2026 | Xint discovers the nginx2root vulnerabilities |
| October 16, 2026 | Xint reports the bugs to F5 through HackerOne |
| October 27, 2026 | Reports reach the nginx development team |
| November 10, 2026 | Xint completes validation of the nginx patches |
| November 18, 2026 | nginx releases 1.30.7 and 1.31.9 fixing ten CVEs, and Xint, Rapid7 and Wiz publish their research |
| November 18, 2026 | Rapid7 publishes a proof of concept for CVE-2026-123007 |
Sources
F5 advisory for CVE-2026-123007
Rapid7 analysis of CVE-2026-123007
Wiz Research on the nginx HTTP/2 vulnerabilities