Blog

Discover the latest news and features of OpenCVE.

NGINX2Root: Affected Versions and Fixes

On November 18, 2026, Xint published NGINX2Root, research covering five NGINX vulnerabilities that can lead to remote code execution in different configurations. The findings affect HTTP/2, HTTP/3, DNS resolution, and mail proxying, putting several everyday NGINX use cases under scrutiny.

If you run NGINX, the first thing to know is that fixes are available: 1.31.9 for the mainline branch and 1.30.7 for the stable branch. You do not have to switch to mainline if you maintain a stable installation.

The next question is which of these vulnerabilities your configuration exposes. They are separate attack paths, and disabling one feature does not necessarily address the whole group.

Last reviewed: November 19, 2026. Package availability and threat intelligence may change after publication.

NGINX2ROOT

NGINX2Root at a glance

CVE Affected area Upstream affected versions*
CVE-2026-123007 HTTP/2 flow-control memory corruption 1.9.5–1.31.8
CVE-2026-123633 HTTP/2 use-after-free 1.19.7–1.31.8
CVE-2026-121810 HTTP/3 use-after-free 1.25.0–1.31.8
CVE-2026-123634 Resolver use-after-free 0.6.18–1.31.8
CVE-2026-113425 Mail proxy use-after-free 0.5.33–1.31.8

These are the ranges listed by NGINX’s security advisories, subject to the affected configuration being used. Fixed releases 1.30.7 and 1.31.9, and vendor builds carrying the fixes, are excluded.

What can an attacker actually do?

The most broadly relevant finding is CVE-2026-123007. It affects NGINX instances accepting HTTP/2 connections. A flaw in how NGINX accounts for flow-control limits can corrupt worker-process memory, causing crashes and potentially allowing code execution.

F5’s CVE description notes that code execution requires ASLR to be disabled or bypassed. That distinction matters: a vulnerable server is not automatically a reliable one-request takeover, but memory corruption in an Internet-facing process still warrants prompt action.

The other findings involve memory being used after it has been freed. For example, the second HTTP/2 flaw affects proxying to a backend when a worker is low on available connections. The resolver flaw involves variable-based upstream names and subrequests resolving the same name. These are different failure conditions, not five steps that an attacker must combine.

The official release notes summarize the underlying defects. For the exploit research and demonstrations, Xint’s full write-up provides the technical detail.

Does NGINX2Root mean immediate root access?

The initial code execution runs with the privileges of the NGINX worker process. Xint demonstrated a further chain using a separate Linux kernel vulnerability in SCTP to obtain host root, including from a container in its test environment.

That is an important result, but it does not mean every affected NGINX instance grants root automatically. The kernel step has its own prerequisites. If you run NGINX in containers, assess the host’s kernel patch status as well as the application image.

How to check your deployment

Start with the binary and configuration used by the service:

nginx -v
nginx -V
sudo nginx -T

These show the version, build options, and configuration files.

For the HTTP/2 paths, look for HTTP/2 support in the build and http2 on; or a legacy http2 parameter on a listen directive. If you use HTTP/3, review QUIC listeners too. For the other paths, check whether you operate a mail proxy or combine runtime DNS resolution with variable-based proxy_pass destinations and SSI or mirror subrequests.

If a CDN or another proxy sits in front, a browser connecting over HTTP/2 only tells you about that frontend. You need to establish what reaches NGINX itself, including directly accessible origin listeners.

Updating NGINX: choose the fix for your installation

For NGINX Open Source, install 1.31.9 mainline or 1.30.7 stable, or a distribution package explicitly patched for these CVEs. Both upstream branches received the five fixes on November 18, as confirmed by the stable release notes.

If you use a distribution package, compare its full package revision with your distributor’s advisory. A backported fix may not change what nginx -v displays. NGINX Plus and products embedding NGINX need their own vendor-specific updates; the Open Source version numbers do not apply to them.

After installing the update, restart NGINX or complete its supported live binary-upgrade procedure. A configuration reload alone does not replace the running executable. For containers, rebuild and replace affected instances so the fixed binary is actually in use.

If you cannot patch immediately

Disabling HTTP/2 temporarily blocks the two HTTP/2 attack paths.

On NGINX 1.25.1 and later, you can set http2 off; in the relevant server blocks and remove legacy http2 parameters from their listen directives. Older versions require removing that listen parameter; they do not support the newer standalone directive. Check every server sharing the affected listening address and port, then validate with nginx -t before applying the configuration. Services requiring HTTP/2, such as native gRPC, need particular care.

This does not mitigate the HTTP/3, resolver, or mail-proxy flaws. Those require changes to their respective features or access paths. If they apply to your deployment, use the configuration-specific guidance in the research and vendor advisories rather than treating HTTP/2 disablement as a complete fix.

Follow NGINX vulnerabilities with OpenCVE

With several CVEs in one disclosure, keeping track of what affects your services can become its own task. OpenCVE helps you follow the products you use, receive CVE updates through automations, and assign vulnerabilities to the people reviewing them.

Manage your Vulnerabilities with OpenCVE

Optimize your CVE management, organize your subscriptions and receive instant notifications with OpenCVE, the vulnerability monitoring platform built for security teams.