---
title: "nginx2root: nginx Vulnerability, Patch 1.31.9 or 1.30.7"
description: "nginx2root is five nginx flaws, led by CVE-2026-123007 in HTTP/2, that can lead to remote code execution. Fixed in nginx 1.31.9 and 1.30.7. Checks and fixes."
url: "https://no7software.co.uk/blog/nginx2root-nginx-vulnerability"
last_modified: "2026-11-19"
---

# nginx2root: nginx Vulnerability, Patch 1.31.9 or 1.30.7

## Key takeaways

- nginx2root is Xint's name for five nginx vulnerabilities that can lead to remote code execution, plus an unpatched Linux kernel flaw that can turn that access into root.
- All five nginx flaws are fixed in nginx 1.31.9 (mainline) and 1.30.7 (stable), released on 18 November 2026; restart nginx after updating, because a reload keeps the old binary.
- The lead flaw, CVE-2026-123007, needs only HTTP/2 to be enabled and affects nginx 1.9.5 to 1.31.8; F5 scores each of the five 9.2 under CVSS 4.0.
- Turning off HTTP/2 blocks two of the five (CVE-2026-123007 and CVE-2026-123633) as a stopgap; the resolver, HTTP/3 and mail proxy flaws need the update or their own mitigations.
- Ubuntu published fixed packages on 19 November 2026 (USN-9159-1); no exploitation was confirmed in CISA's catalogue when we checked that day.

### Update, 19 November 2026, 16:20 UTC: Debian fixes nginx in Debian 13 (DSA-6642-1)

Debian has published [DSA-6642-1](https://security-tracker.debian.org/tracker/DSA-6642-1), a security update for nginx in Debian 13 (trixie). The tracker lists the fixed package as `1.26.3-3+deb13u11` and names all five nginx2root CVEs among the nine it covers. On Debian 13, install the update with `sudo apt update && sudo apt upgrade`, restart nginx, and confirm the package version with `dpkg -l nginx`.

Debian 12 (bookworm) is still listed as vulnerable on the [Debian tracker page for CVE-2026-123007](https://security-tracker.debian.org/tracker/CVE-2026-123007), with no fixed package shown yet. Until one is published, apply the mitigations below on Debian 12 servers.

**nginx2root** is the name the security firm Xint gave to five vulnerabilities in the nginx web server that can lead to remote code execution, plus one unpatched Linux kernel flaw that turns that access into root. The nginx team fixed all five in **nginx 1.31.9** (mainline) and **nginx 1.30.7** (stable), released on 18 November 2026. The most serious is [CVE-2026-123007](https://www.cve.org/CVERecord?id=CVE-2026-123007). **CVE-2026-123007** is a memory corruption flaw in the way nginx handles HTTP/2 flow control. It needs only HTTP/2 to be enabled and affects every release from 1.9.5 to 1.31.8. If nginx sits in front of your store, API or app, update it and restart it now.

## What is nginx2root?

[Xint's write-up](https://xint.io/blog/nginx2root-remote-code-execution), published on 18 November 2026, describes five nginx vulnerabilities that are separate attack paths: each affects a different configuration, and they do not need to be chained together. Xint says the worst of them lets an attacker who has not logged in run commands on the server with the privileges of the nginx worker process. Xint also found a flaw in the Linux kernel's SCTP subsystem and used it to go from the worker process to root, including from inside a Docker container to the host. It calls the six vulnerabilities together nginx2root.

F5, which maintains nginx, published the CVE records the same day. Each of the five carries a CVSS 4.0 score of 9.2 (Critical) and a CVSS 3.1 score of 8.1 (High). F5's wording is more cautious than Xint's. Every record says an attacker can execute code on systems where ASLR is disabled or where the attacker can bypass it. Otherwise the records describe a crash of the worker process or memory corruption. **ASLR** is Address Space Layout Randomization, a memory protection that places code and data at unpredictable addresses so an attacker cannot easily find them. The lead flaw was reported by more than one team. F5 credits Rapid7, Wiz Research, Xint and Ikotas Labs for CVE-2026-123007.

## Which nginx versions are vulnerable?

The [nginx security advisories page](https://nginx.org/en/security_advisories.html) lists the affected ranges below. All five are fixed in 1.31.9 and 1.30.7, which are the latest nginx versions on the mainline and stable branches as of 19 November 2026. The severity column is nginx's own rating, which differs from the CVSS scores in the CVE records.

| CVE | Where the flaw is | Vulnerable versions | nginx severity |
| --- | --- | --- | --- |
| [CVE-2026-123007](https://www.cve.org/CVERecord?id=CVE-2026-123007) | HTTP/2 flow control: memory corruption when HTTP/2 is enabled | 1.9.5 to 1.31.8 | Major |
| [CVE-2026-123633](https://www.cve.org/CVERecord?id=CVE-2026-123633) | HTTP/2: use-after-free when requests are proxied to a backend and the worker is running low on `worker_connections` | 1.19.7 to 1.31.8 | Medium |
| [CVE-2026-123634](https://www.cve.org/CVERecord?id=CVE-2026-123634) | Resolver: use-after-free when the same name is resolved at the same time in subrequests | 0.6.18 to 1.31.8 | Medium |
| [CVE-2026-121810](https://www.cve.org/CVERecord?id=CVE-2026-121810) | HTTP/3: use-after-free | 1.25.0 to 1.31.8 | Medium |
| [CVE-2026-113425](https://www.cve.org/CVERecord?id=CVE-2026-113425) | Mail proxy module: use-after-free | 0.5.33 to 1.31.8 | Major |

F5's CVE records list NGINX Plus as affected as well, and note that versions past End of Technical Support were not evaluated. If you run NGINX Plus or another F5 product built on nginx, use the F5 advisory linked from each CVE record for the fixed release.

The same two releases fix five more issues that are not part of nginx2root, according to the [nginx change log](https://nginx.org/en/CHANGES):

- **CVE-2026-118899**, rated major: an endless loop while reading a request body over TLS 1.3.
- **CVE-2026-120967**: a client certificate check in the stream module that could use the wrong server configuration.
- **CVE-2026-125283**: a buffer overflow with `try_files` and `alias`.
- **CVE-2026-120993**: a crash with PROXY protocol version 2.
- **CVE-2026-123640**: a parsing difference in the stream `ssl_preread` module.

## How to check your nginx version and exposure

Check three things on every server, container image and load balancer that runs nginx.

1. **The version.** Run `nginx -v`. Anything from 1.9.5 to 1.31.8 is in range for CVE-2026-123007 unless your distribution has backported the fix.
2. **The package version on Linux distributions.** Distributions patch nginx without changing the number that `nginx -v` prints, so compare the full package version with the distribution's notice. On Debian and Ubuntu, `dpkg -l nginx` shows it.
3. **Whether HTTP/2 is on.** Run `nginx -T | grep -n http2` to find `http2` in the loaded configuration. Xint suggests confirming from outside with `openssl s_client -connect HOST:443 -servername HOST -alpn h2` and looking for the line `ALPN protocol: h2`.

Xint counted 56.7 million hosts identifying as nginx on Shodan on 10 November 2026. Of the 11.94 million that reported a version, 98.9% ([Xint, 18 November 2026](https://xint.io/blog/nginx2root-remote-code-execution)) were in the range affected by CVE-2026-123007. Xint notes that this does not prove a server is vulnerable, because the flaw also needs HTTP/2 and a reported version may already include a backported fix.

## How to fix nginx2root

1. **Upgrade nginx.** Move to 1.31.9 on the mainline branch or 1.30.7 on the stable branch, or install your distribution's patched package.
2. **Restart, do not just reload.** Xint points out that a configuration reload does not replace the running executable. Restart nginx, for example with `sudo systemctl restart nginx` on a systemd server, or complete a supported live binary upgrade. Then check the version again.
3. **Rebuild container images.** A container keeps the nginx it was built with. Pull or rebuild the image with a fixed nginx and redeploy.
4. **Check everything that embeds nginx.** Ingress controllers, API gateways and control panels often ship their own nginx build. Each needs its own vendor update.

### Distribution packages

| Distribution | Status on 19 November 2026 | Source |
| --- | --- | --- |
| Ubuntu | USN-9159-1, published on 19 November 2026, covers all five CVEs. Fixed packages include `1.24.0-2ubuntu7.20` for 24.04 LTS, `1.18.0-6ubuntu14.23` for 22.04 LTS and `1.28.3-2ubuntu1.13` for 26.04 LTS. | [Ubuntu security notice](https://ubuntu.com/security/notices/USN-9159-1) |
| Debian | The tracker lists bookworm and trixie as vulnerable and unstable as fixed in `1.30.6-4`. | [Debian security tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007) |
| Red Hat | Red Hat rates CVE-2026-123007 Critical and lists nginx on RHEL 8, 9 and 10 as affected, with no fixed package listed yet. | [Red Hat CVE page](https://access.redhat.com/security/cve/CVE-2026-123007) |

## Mitigations if you cannot patch today

These reduce exposure until the update is installed. None of them replaces it.

- **Turn off HTTP/2.** Xint says this blocks CVE-2026-123007 and CVE-2026-123633, but not the other three. On nginx 1.25.1 and later, set `http2 off;` in each affected server block and remove any `http2` parameter from `listen` directives. On 1.9.5 to 1.25.0, remove `http2` from the `listen` line. Run `nginx -t`, then reload. Browsers fall back to HTTP/1.1; services that need HTTP/2, such as native gRPC, will stop working.
- **Resolver flaw.** F5's workaround for CVE-2026-123634 is to avoid SSI and `mirror` directives and to avoid a proxied server name that contains variables. Xint adds that pointing `proxy_pass` at a fixed upstream group removes the DNS lookup made during the request.
- **HTTP/3.** Neither F5 nor nginx lists a workaround for CVE-2026-121810. If you cannot patch, the remaining option is to stop serving HTTP/3 until you can.
- **Mail proxy.** F5's workaround for CVE-2026-113425 is to restrict the mail proxy listeners to trusted networks.

## The Linux kernel half of the chain

The nginx flaws give an attacker the worker process, which normally runs as an unprivileged user. Xint says it reached root by chaining a separate use-after-free in the Linux kernel's SCTP send path, and that the same chain escaped a Docker container. Xint describes that kernel flaw as a zero-day with no patch available when it published, and has withheld most of the details. **SCTP** is the Stream Control Transmission Protocol, a transport protocol that sits alongside TCP and UDP in the Linux kernel.

Until a kernel fix exists, Xint's advice for hosts that do not use SCTP is to stop the module loading by placing `install sctp /bin/false` in a modprobe configuration file. It warns that this does not unload a module that is already loaded and does not help where SCTP is compiled into the kernel. This is a different bug from the [Linux kernel TCP flaw CVE-2026-98432](https://no7software.co.uk/blog/linux-kernel-cve-2026-98432-tcp-vulnerability) we covered earlier this month.

## Is nginx2root being exploited?

No exploitation had been confirmed by the official sources we checked on 19 November 2026. None of the five CVEs is in the [CISA Known Exploited Vulnerabilities catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) (version 2026.11.18), and the CISA assessment attached to each CVE record lists exploitation as none. Xint says it left out the final steps needed to reproduce its exploits.

That can change quickly. Xint notes that an attack on CVE-2026-123007 may leave little in nginx access logs, because the HTTP/2 control frames used to trigger it are not logged as requests. It names a program started by an nginx worker as the clearest sign of a successful attack, and repeated abnormal worker exits as a weaker one.

## What this means for ecommerce sites

nginx is the usual front door for self-hosted Magento and WooCommerce stores, for headless storefronts and for the back ends of custom apps. On those stacks the web server terminates TLS and sees every request, so code running in a worker process is close to customer and order data.

- **Self-hosted stores.** Patch the server, the staging copy and any build or cron hosts that run nginx. If the stack also runs PHP, the [PHP2Shell vulnerabilities](https://no7software.co.uk/blog/php2shell-php-vulnerability) need the same attention.
- **Managed hosting.** Ask your host whether its nginx build includes the fixes for all five CVEs and when it was restarted.
- **Shopify and BigCommerce.** The storefront is run by the platform, so there is nothing for a merchant to patch there. Custom apps, middleware and headless front ends that you host yourself are still your responsibility.

## Timeline

- **11 October 2026:** Xint says its research team discovered the vulnerabilities.
- **16 October 2026:** Xint reported them to F5 through HackerOne.
- **27 October 2026:** the reports reached F5's nginx development team.
- **10 November 2026:** Xint completed validation of the patches.
- **18 November 2026:** nginx 1.31.9 and 1.30.7 were released, and F5 published the CVE records.
- **19 November 2026:** Ubuntu published USN-9159-1 with fixed packages.

## Sources and methodology

This post is a summary of public sources, not our own exploit research. Fact check: every version number, CVE identifier, score and date above was checked on 19 November 2026 against the page it links to. The sources are the [nginx security advisories](https://nginx.org/en/security_advisories.html) and change log, the CVE records published by F5, [Xint's research post](https://xint.io/blog/nginx2root-remote-code-execution), the Ubuntu, Debian and Red Hat security trackers, and the CISA catalogue. Where F5 and Xint describe the impact differently, both descriptions are given. Reports of public exploit code that we could not confirm in those sources are left out. This post will be updated as distributions release fixes. No7 Software is an ecommerce engineering agency; you can read more [about us](https://no7software.co.uk/about).

## What to do next

List every place nginx runs, upgrade each one to 1.31.9, 1.30.7 or a patched distribution package, and restart it. Where you cannot do that today, turn off HTTP/2 and work through the other mitigations above, then schedule the update. If you want your store's servers checked and patched for you, [get in touch with our team](https://no7software.co.uk/contact).

## Frequently Asked Questions

The questions buyers and engineers ask us most about this topic.

### What is the nginx2root vulnerability?

nginx2root is the name the security firm Xint gave to five vulnerabilities in the nginx web server that can lead to remote code execution. They are CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. Xint also chained a separate Linux kernel flaw to gain root. nginx fixed the five nginx flaws on 18 November 2026.

### Which nginx version fixes nginx2root?

nginx 1.31.9 on the mainline branch and nginx 1.30.7 on the stable branch, both released on 18 November 2026. Linux distributions ship their own patched packages. Ubuntu published them in USN-9159-1 on 19 November 2026.

### What is the latest nginx version?

As of 19 November 2026, the latest nginx versions are 1.31.9 on the mainline branch and 1.30.7 on the stable branch, according to nginx.org. Both were released on 18 November 2026 and include the nginx2root fixes.

### Which nginx versions are affected by CVE-2026-123007?

The nginx security advisories page lists 1.9.5 to 1.31.8 as vulnerable, which is every release since HTTP/2 support was added. The flaw is reached only when HTTP/2 is enabled.

### How do I check which nginx version I am running?

Run nginx -v on the server; it prints the nginx version. On Linux distributions also check the full package version, for example with dpkg -l nginx on Debian and Ubuntu, because distributions backport security fixes without changing the number nginx -v reports. Run nginx -T | grep -n http2 to see whether HTTP/2 is enabled.

### Is nginx 1.24.0 on Ubuntu 24.04 vulnerable to nginx2root?

It depends on the package version, not the 1.24.0 number. Ubuntu fixed the five nginx2root CVEs in USN-9159-1 on 19 November 2026; the fixed package for Ubuntu 24.04 LTS is 1.24.0-2ubuntu7.20 and for 22.04 LTS it is 1.18.0-6ubuntu14.23. Earlier package versions are affected, so update and restart nginx.

### Does disabling HTTP/2 fix nginx2root?

Only partly. Xint says turning off HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633, but not the resolver, HTTP/3 or mail proxy flaws. It is a temporary measure until nginx is updated.

### Do I need to restart nginx after updating?

Yes. Xint notes that a configuration reload does not replace the running executable. Restart nginx, for example with sudo systemctl restart nginx, or complete a supported live binary upgrade. Rebuild any container images that include nginx as well.

### Is nginx2root exploited in the wild?

No exploitation had been confirmed by official sources on 19 November 2026. None of the five CVEs was in the CISA Known Exploited Vulnerabilities catalog, and the CISA assessment in each CVE record listed exploitation as none.

### Does nginx2root affect Shopify stores?

Not the Shopify storefront itself, which Shopify runs and maintains. Custom apps, middleware and headless front ends that you host on your own servers behind nginx need the update.
