On November 18, 2026, the nginx team released nginx 1.31.9 (mainline) and 1.30.7 (stable), which fix ten vulnerabilities, five of which, according to research company Xint, allow an unauthenticated attacker to remotely execute arbitrary code with the privileges of the nginx worker process. The set of vulnerabilities has been named NGINX2Root: Xint reports that by combining one of them with a separate bug in the Linux kernel, they were able to obtain root access on the host — including when nginx is running inside a Docker container. Each of the five vulnerabilities is exploitable independently and affects different configurations. At the time of disclosure, no exploitation in the wild had been observed. All nginx administrators are strongly advised to update immediately and restart the service.
Five vulnerabilities: technical details
According to the official nginx advisories, the vulnerabilities are as follows:
- CVE-2026-123007 — memory corruption in the HTTP/2 flow control mechanism. Severity level per nginx: major. Affected versions are 1.9.5 through 1.31.8 — effectively every release since HTTP/2 support was introduced in 2015. Requires HTTP/2 to be enabled. Xint calls this vulnerability the most critical in the set.
- CVE-2026-123633 — use-after-free in HTTP/2. Affected versions are 1.19.7–1.31.8. Requires proxying requests to an upstream server. Severity level: medium.
- CVE-2026-121810 — use-after-free in HTTP/3. Affected versions are 1.25.0–1.31.8. Also requires proxying to an upstream. Severity level: medium.
- CVE-2026-123634 — use-after-free when processing responses in the resolver. Nginx lists the affected range as 0.6.18–1.31.8. Exploitation requires the
resolverdirective, an address forproxy_passthat is dynamically generated from the request, and the attacker’s ability to control the authoritative DNS server that nginx queries. Severity level: medium. - CVE-2026-113425 — use-after-free in the mail proxy module. Affected versions are 0.5.33–1.31.8. Requires a configuration with
proxy onandauth_http. According to Xint, exploitation worked even when all authentication attempts were rejected. Severity level: major.
It is important to note a discrepancy in severity assessment: Xint characterizes all five vulnerabilities collectively as critical, while nginx in its own advisories assigns two of them the level major (CVE-2026-123007 and CVE-2026-113425) and three — medium. This difference matters for prioritization: the vendor classification is based on individual CVEs, whereas the researchers’ classification is based on the combined potential of an attack chain.
Additional fixes
The same releases also fix five more vulnerabilities: CVE-2026-118899 (infinite loop when reading the request body over TLS 1.3, major), CVE-2026-120993 (null pointer dereference with PROXY protocol v2), CVE-2026-125283 (buffer overflow when using alias and try_files), CVE-2026-120967 (SNI bypass when validating client certificates in stream), and CVE-2026-123640 (insufficient validation in the ssl_preread module for stream).
The chain to root: Linux kernel vulnerability
According to Xint, the researchers combined CVE-2026-123007 with a separate use-after-free vulnerability in the SCTP implementation in the Linux kernel, present starting from kernel version 4.15 (2018). The result is obtaining root privileges on the host, including in a Docker container escape scenario. As of the time of publication, this kernel vulnerability does not have an assigned CVE and has not been fixed; Xint is withholding technical details until a patch is released. There is no independent confirmation of these results in the available materials — the data is based solely on Xint’s lab tests.
We have previously analyzed vulnerabilities in HTTP/2 implementations in nginx and other servers — in the context of DoS attacks via HPACK. The current set of vulnerabilities is fundamentally different: this is not about denial of service but about full-fledged remote code execution.
Impact assessment
Nginx is one of the most widespread web servers and reverse proxies in the world. CVE-2026-123007 affects all versions with HTTP/2 support released over the past 11 years. This means that the overwhelming majority of production installations with HTTP/2 enabled are potentially vulnerable. The other four vulnerabilities have more specific configuration prerequisites (HTTP/3, upstream proxying, dynamic DNS, mail proxy), but together they cover typical nginx deployment scenarios.
The lack of any authentication requirement makes all five vulnerabilities accessible to any attacker capable of sending a request to the target server. If the SCTP vulnerability in the Linux kernel remains unpatched, the potential consequences go beyond compromising the web server — up to full control over the host.
Mitigation recommendations
The primary action is to update to nginx 1.31.9 or 1.30.7 followed by a full restart of the service. According to Xint, a simple configuration reload is not sufficient: existing connections (HTTP/2, mail sessions) continue to be served by old worker processes containing vulnerable code. Distribution packages may include backported fixes — check the advisories for your specific distribution.
Temporary measures until you can update:
- Disable HTTP/2 — blocks CVE-2026-123007 and CVE-2026-123633, but does not protect against the other three vulnerabilities
- Disable HTTP/3 — blocks CVE-2026-121810
- Remove dynamic DNS resolution at runtime (request-time DNS lookups) — reduces the risk of CVE-2026-123634
- Restrict access to the mail proxy — reduces the risk of CVE-2026-113425
- Block the SCTP kernel module via
modprobeon hosts where SCTP is not used — reduces the risk of escalation to root
Signs of possible compromise
Xint highlights the following indicators worth checking:
- Programs unexpectedly launched under the nginx worker process account — the clearest sign of a successful attack
- Persistently high inbound traffic or many connections from a single source
- A significant discrepancy between the volume of bytes received and the request length in the logs
- Repeated abnormal terminations of worker processes
Each of these signals on its own may have a benign explanation and needs to be correlated with other data.
Given the scale of the affected versions, the absence of authentication requirements, and the root-level privilege escalation demonstrated by the researchers, updating nginx to versions 1.31.9 or 1.30.7 with a full service restart should be treated as a top priority. Administrators of Linux servers running nginx are additionally advised to block the SCTP module until a kernel patch is released and to review logs for the anomalies described above.












