If your website runs on NGINX, two critical vulnerabilities disclosed this week need your attention today. Dubbed “nginx2root”, the flaws let unauthenticated attackers run code on vulnerable web servers, and researchers have already shown how to chain one of them with a Linux kernel bug to get root on the host. The bugs affect NGINX versions going back to 2015, and fixes are already out. Here is exactly what is affected, how to check your server, and what to do if you cannot upgrade immediately.
What Is the NGINX2Root Vulnerability?
The name covers two critical HTTP/2 flaws found independently by researchers at Xint, Wiz, Ikotas Labs, Metnir and Rapid7. Xint also found three more remote code execution bugs in NGINX, and Censys later reproduced the underlying memory corruption conditions in four of the five flaws in lab testing.
- CVE-2026-123007: a flow-control bug that corrupts memory in an NGINX worker. It affects all versions from 1.9.5 (released in 2015) through 1.31.8. Wiz demonstrated unauthenticated remote code execution on a server hosting ordinary static files over HTTP/2 with TLS.
- CVE-2026-123633: a use-after-free bug that triggers when NGINX accepts HTTP/2 connections and proxies requests to a backend. It affects versions 1.19.7 through 1.31.8. When the worker runs low on connection slots, it can close an active connection and free memory that a request is still using.
The “2root” part comes from Xint’s demonstration: they chained CVE-2026-123007 with a separate Linux kernel flaw in the SCTP subsystem to escape an NGINX Docker container and gain root on the underlying host. The three additional use-after-free flaws are CVE-2026-121810 (HTTP/3 reverse proxying), CVE-2026-123634 (DNS resolution with subrequests) and CVE-2026-113425 (mail proxy authentication).
Wiz has not published its proof-of-concept exploits, but the details are public enough that assume capable attackers are already working on them.
Which Versions Are Affected?
- NGINX Open Source: anything from 1.9.5 up to 1.31.8 for CVE-2026-123007, and 1.19.7 to 1.31.8 for CVE-2026-123633. The fixes ship in 1.30.7 stable and 1.31.9 mainline.
- NGINX Plus: update to 37.0.8.1 or 37.3.0.1.
- Also fixed in the same advisory: CVE-2026-118899, a high-severity denial of service where an unauthenticated attacker can make a worker enter an infinite loop while reading a request body over TLS 1.3.
The exposure numbers sound scary but need context. Xint reported that 98.9% of NGINX hosts disclosing recognizable versions were running a version in the affected range. Security researcher Florian Roth, commenting on X, called the flaws worse than the recent Node2Shell and Java2Shell issues but said they are exploitable in non-default configurations and are not an imminent threat for most deployments. Version numbers alone are misleading, because distributions backport fixes and not every server has HTTP/2 enabled. Roth’s Shodan sample found roughly 66% of NGINX HTTPS endpoints supporting HTTP/2.
How Does This Compare to Node2Shell and Java2Shell?
If those names are unfamiliar, they were the last two “tool-to-root” scares: remote code execution chains in Node.js and Java respectively that lit up security feeds and generated a wave of panic scanning. Florian Roth’s framing of nginx2Root is useful for calibrating your response. It is technically worse, because the chain can reach root on the host and the bugs sit in a far more widely deployed piece of software, but the real-world conditions required are narrower than the version numbers suggest.
Two things separate this from a mass-exploitation event just yet. The main proof-of-concept exploits from Wiz and Xint are not public, and both HTTP/2 flaws need a configuration that, while common, is not universal. What history with Node2Shell and Java2Shell taught everyone is that the quiet period does not last. Scanning for vulnerable endpoints typically starts within days of advisories landing, and the internet-wide scan traffic for NGINX version strings has likely already begun.

How to Check If Your Server Is Vulnerable
Three conditions decide your real risk. The two HTTP/2 flaws need an unpatched server with HTTP/2 enabled on a listener an attacker can reach, and CVE-2026-123633 additionally needs NGINX proxying requests to a backend. Run these checks:
- Check your version:
nginx -vornginx -V. If it is below 1.30.7 or 1.31.9, check your distro’s changelog to see whether a backported fix is already applied. - Check for HTTP/2:
nginx -T 2>/dev/null | grep -i http2shows whether any server block enables it. You can also probe a site withcurl --http2 -sI https://yoursite.comand look for the HTTP/2 response line. - Check for reverse proxying: look for
proxy_passin your NGINX config, which is the extra condition for CVE-2026-123633. - Check your distro’s advisory even if the version looks old. Debian, Ubuntu and RHEL frequently backport security fixes without bumping the version string.
How to Protect Your NGINX Server
- Upgrade now. Move to NGINX Open Source 1.30.7 stable or 1.31.9 mainline, or NGINX Plus 37.0.8.1 or 37.3.0.1. This is the only fix that covers all five RCE flaws plus the TLS denial of service.
- Cannot upgrade today? Disable HTTP/2. Remove the
http2flag from your listener directives and reload withnginx -s reload. This stops the two nginx2root flaws specifically, but it is not a substitute for patching, and it leaves the other bugs in place. - Update your container images and hosts. If you run NGINX in Docker, rebuild the image with the patched version and patch the host kernel too. The root escape Xint demonstrated relies on a Linux kernel SCTP flaw.
- Review your exposure. Anything internet-facing with HTTP/2 and reverse proxying is the highest risk combination. Internal NGINX instances are lower risk but should still be patched.
- Watch the F5 advisory page. The full batch of fixes is tracked on nginx.org’s security advisories page, and more detail may land as researchers publish deeper analysis.
Frequently Asked Questions
What is the NGINX2Root vulnerability?
It is a pair of critical HTTP/2 flaws in NGINX, CVE-2026-123007 and CVE-2026-123633, that allow unauthenticated remote code execution. Researchers showed one of them can be chained with a Linux kernel bug to gain root access on the host server.
Which NGINX versions are affected?
CVE-2026-123007 affects NGINX 1.9.5 through 1.31.8, and CVE-2026-123633 affects 1.19.7 through 1.31.8. Fixed versions are 1.30.7 stable and 1.31.9 mainline for open source, and 37.0.8.1 or 37.3.0.1 for NGINX Plus.
How do I check if my server is vulnerable?
Run nginx -v to check the version, grep your config for http2 and proxy_pass, and verify your distribution’s security changelog for backported fixes. An unpatched server with HTTP/2 enabled on a public listener is the highest risk case.
Is NGINX2Root being exploited in the wild?
No mass exploitation has been confirmed yet, and the main proof-of-concept exploits are not public. But the technical details are out, the fix is available, and researchers rate the flaws as serious, so patch before that changes.
