TLDR;
- nginx2root is a set of five nginx remote code execution (RCE) vulnerabilities, led by CVE-2026-123007 in HTTP/2 handling, plus a Linux kernel SCTP flaw that can lift a worker foothold to host root.
- The researchers rate the set Critical, but CVSS scores aren’t published yet.
- CVE-2026-123007 affects every official nginx release from 1.9.5 through 1.31.8 when HTTP/2 is enabled.
- nginx 1.31.9 is the fixed release, scheduled for November 19, 2026.
- Until it ships, disable HTTP/2 and the other affected features listed under Workaround.
- nginx2root was discovered and reported by Xint researchers @imssm99, @cdor1, @tjbecker, and @yves.
nginx2root is the name given to five independent nginx vulnerabilities and one Linux kernel flaw, published on November 18, 2026. nginx is a widely deployed web server and reverse proxy.
Each of the five nginx flaws lets an unauthenticated remote attacker run commands with the privileges of an nginx worker process, in different configurations: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425. CVE-2026-123007 reaches the most servers because it only needs HTTP/2 enabled. The researchers chained it with a separate Linux kernel SCTP flaw to gain root on the host, including from inside a Docker container.
Technical Details of CVE-2026-123007
CVE-2026-123007 is an integer overflow in HTTP/2 flow control. nginx subtracts queued response data from the connection send window and returns that credit when a stream is cancelled before the data is sent.
A client can raise the window with WINDOW_UPDATE frames while data waits in the queue, then cancel the streams, so cleanup adds the credit a second time without checking the protocol maximum. The window then exceeds its limit, the capacity check underflows, and later updates keep growing it.
A signed and unsigned conversion finally produces an enormous copy length, which corrupts heap metadata and discloses addresses. The researchers used this to run commands as the worker over a public port on AWS, GCP, and Azure. No authentication or user interaction is required.
The other four are use-after-free bugs. CVE-2026-123634 sits in the DNS resolver and needs request-time resolution plus the mirror directive. CVE-2026-123633 (HTTP/2) and CVE-2026-121810 (HTTP/3) arise when connection draining frees a request that is still running. CVE-2026-113425 affects the mail proxy during auth_http logins. The kernel flaw is a use-after-free or double free in the SCTP send path, present since Linux 4.15. The sources list no CVE ID or kernel patch for it.
Affected Products or Versions by nginx2root
CVE-2026-123007 spans every official release from 1.9.5 through 1.31.8, and the master branch carried the vulnerable code on November 10, 2026. Distributions may backport fixes without changing the nginx version string, so compare the full package version with the distribution advisory.
- CVE-2026-123007: HTTP/2 enabled, from 1.9.5.
- CVE-2026-123634: resolver, request-derived proxy_pass, and mirror with mirror_request_body off, from 1.13.4.
- CVE-2026-123633: HTTP/2 with upstream forwarding, from 1.19.7.
- CVE-2026-121810: HTTP/3 with upstream forwarding, from 1.25.0.
- CVE-2026-113425: mail proxy using proxy on and auth_http, from 0.5.15.
- Fixed version: 1.31.9.
- Not affected by CVE-2026-123007: 1.9.4 and earlier, or builds without the HTTP/2 module.
- Kernel SCTP flaw: Linux 4.15 onward, unpatched at publication.
Impact if exploited: Commands run as the nginx worker. Root on the host needs the kernel SCTP flaw, which was unpatched at publication. Containers share the host kernel, so a successful kernel exploit reaches every container on that host.
Are We Exploitable by nginx2root?
The answer depends on your configuration. The ratings below are our own reading of the published research and will change as more information arrives.
| CVE | Condition for exposure | Realistic chance | Technical basis |
|---|---|---|---|
| CVE-2026-123007 | Unpatched 1.9.5 to 1.31.8, HTTP/2 module built in, HTTP/2 reachable | High when all three hold | Needs only a TLS port that negotiates h2. Success was shown from a public IP on AWS, GCP, and Azure, under concurrent normal traffic. |
| CVE-2026-123633 | HTTP/2 with proxy_pass | Moderate | The attacker must fill the worker’s connection slots (draining starts at 1/16 free or fewer), and nginx must be able to open a TCP connection to the attacker. |
| CVE-2026-121810 | HTTP/3 (QUIC) listener with upstream forwarding | Low to moderate | Needs UDP 443 exposed, the same slot pressure, and outbound TCP to the attacker. |
| CVE-2026-123634 | resolver, variable proxy_pass, and mirror | Low | An uncommon configuration. The nginx resolver must also reach an attacker-controlled DNS server. |
| CVE-2026-113425 | Mail proxy with auth_http | Low | Applies only to mail proxy deployments. No credentials are needed. |
| Kernel SCTP flaw | Worker code execution plus reachable SCTP | Moderate after a successful nginx exploit | Many distributions autoload the SCTP module. Reachability depends on the kernel, modules, and container restrictions. |
Why does CVE-2026-123007 carry the highest chance?
The attack uses standard HTTP/2 frames (SETTINGS, PING, WINDOW_UPDATE, RST_STREAM) over a long-lived TLS connection. It needs no credentials and no special directive. Among hosts that report a version, 98.9% of 11.94 million Shodan results fall inside the affected range. That figure counts version strings only, so backported fixes and disabled HTTP/2 will lower the real number.
What slows attackers down?
The writeup withholds the final exploitation steps. The demonstrated chain relies on glibc’s x86-64 memcpy behavior (a backward-copy loop present since glibc 2.24) and on heap grooming through Range and Cookie headers. The sources do not cover reliability on other architectures or C libraries. The walkthrough is detailed, so we expect skilled attackers to reproduce it over time.
If your version is in range (or a backport is unverified), the HTTP/2 module is present, and ALPN protocol: h2 appears on the real nginx port, treat the server as exploitable and apply the Workaround now.
Detection for nginx2root
Exposure for CVE-2026-123007 depends on version, module, and configuration. Attack traces are sparse because the HTTP/2 control frames are encrypted and absent from access logs, so combine several signals.
- Run
nginx -vandnginx -Vto check the version and the--with-http_v2_moduleflag. - Run
sudo nginx -Tand search forhttp2inlistendirectives orhttp2 on;. - From outside, run
openssl s_client -alpn h2.ALPN protocol: h2means HTTP/2 is reachable. - Compare
ss -tinpcounters over time. Long-lived connections with fast-growingbytes_receivedand littlebytes_sentmatch the tested attack. - Add an
auditdrule forexecveby the worker UID. A shell started by a worker is the clearest sign of compromise. - Check
error.logandcoredumpctl list nginxfor worker crashes. - The research publishes no IOCs such as IP addresses or file hashes.
Mitigation for nginx2root
Update to nginx 1.31.9 once it is released (scheduled for November 19, 2026) and confirm the build includes fixes for all five CVEs. For distribution packages, compare the full package version with the distribution’s security advisory.
The research points to the nginx vendor advisory K000164058 for patch details. After installing, restart nginx or complete a live binary upgrade, because a configuration reload does not replace the running executable. Apply the Linux kernel fix for the SCTP flaw when one is available.
Workaround for nginx2root
The research lists temporary measures for each path. They remain temporary until the patch is installed.
- CVE-2026-123007 and CVE-2026-123633: disable HTTP/2 on affected ports (
http2 off;on 1.25.1 and later, removehttp2fromlistenon older releases). Native gRPC services will be affected. - CVE-2026-123634: point
proxy_passat a fixed upstream group and turn offmirrorif unused. Other subrequest features such as SSI may reach the same bug. - CVE-2026-121810: remove
quiclisteners, sethttp3 off;, and sendAlt-Svc 'clear'. - CVE-2026-113425: bind mail listeners to a loopback address or allow only trusted IPs through the firewall.
- Kernel SCTP flaw: on hosts that do not use SCTP, add
install sctp /bin/falseunder/etc/modprobe.d/. This leaves an already loaded module and built-in SCTP in place.
How Astra Helps

When a flaw like nginx2root drops, the first question is simple: where is nginx running in our environment? Astra helps you answer it fast.
We are watching the nginx advisories, distribution advisories, and CISA KEV, and we will add scanner coverage and detections across Astra DAST, API Security Testing, and the Cloud Scanner as soon as there is enough confirmed information. This page will be updated when that happens.
You can start preparing today if you run Continuous Pentest or Autonomous Pentesting:
- Find your nginx hosts: API discovery lists every HTTP-reachable endpoint and the stack behind it, so one query shows which hosts run nginx.
- Verify your fixes: Our pentest team can run a scoped retest on your nginx attack surface once the patch is out.
Think nginx2root might affect you? Talk to our team.
Disclaimer: This advisory reflects information available as of November 18, 2026, 9:12 PM IST. nginx2root is an evolving situation, and we will update this page as more information comes in.
Sources: nginx2root.com; nginx2root research writeup (xint.io/blog/nginx2root-remote-code-execution), published November 18, 2026. Research credit: @imssm99, @cdor1, @tjbecker, and @yves.



