Back to all articles

NGINX2Root: five NGINX RCE flaws, patches and Linux checks

Share

An NGINX reverse proxy can be compromised even when the applications behind it have no known vulnerabilities. On 18 November 2026, F5 and the NGINX project fixed ten security issues affecting NGINX Open Source and NGINX Plus. Five memory-corruption vulnerabilities collectively named NGINX2Root can, under specific conditions, allow unauthenticated remote code execution (RCE).

The most broadly exposed vulnerability is CVE-2026-123007, a flaw in HTTP/2 flow control: a vulnerable NGINX server directly accepting HTTP/2 connections can reach the problematic code path. Another HTTP/2 vulnerability, CVE-2026-123633, involves certain reverse-proxy conditions. Three others concern HTTP/3/QUIC, DNS resolution with subrequests, and NGINX's mail proxy.

France's CERT-FR alert of 18 November confirms that a public proof of concept exists for CVE-2026-123007. CERT-EU security advisory 2026-022 calls for urgent patching, prioritizing internet-facing installations. As of 19 November 2026, the official sources reviewed do not establish any successful exploitation in the wild. Laboratory demonstrations are not evidence that a real-world victim has already been compromised.

Top priority: patch NGINX and restart its workers. Disabling HTTP/2 is useful as temporary risk reduction for two CVEs, but it does not address every NGINX2Root vulnerability.

Why one vulnerable reverse proxy can expose many services

NGINX often sits at the network edge, terminating TLS, serving files or passing requests to PHP-FPM, Node.js, APIs, admin interfaces and multiple internal applications.

These vulnerabilities can be triggered while NGINX itself is processing network protocols, before the request reaches application logic. The underlying problems include faulty HTTP/2 flow-window calculations and memory objects that are written out of bounds or accessed after release (use-after-free).

Wiz Research demonstrated CVE-2026-123007 in a laboratory against NGINX serving static files, with no vulnerable backend application. Rapid7 independently demonstrated it in an NGINX 1.31.8 container.

The NGINX2Root name does not mean exploitation automatically grants root access. These flaws may allow code execution with the privileges of an NGINX worker process. Obtaining root on the host or escaping a container requires additional circumstances, rights or vulnerabilities.

The five principal vulnerabilities and prerequisites

CVE Component Significant prerequisites Possible impact
CVE-2026-123007 HTTP/2 flow control HTTP/2 enabled on directly reachable NGINX; no backend required Heap corruption, worker crash, RCE
CVE-2026-123633 HTTP/2 use-after-free HTTP/2 reverse proxy, particularly connection-draining and connection-exhaustion conditions Memory corruption, RCE
CVE-2026-121810 HTTP/3/QUIC use-after-free HTTP/3 enabled and relevant upstream connection handling Memory corruption, RCE
CVE-2026-123634 DNS resolver use-after-free Dynamic upstream name resolution alongside particular SSI or mirror subrequests Memory corruption, RCE
CVE-2026-113425 Mail proxy use-after-free Mail proxy module using auth_http Memory corruption, RCE

F5 rated these five flaws 8.1/10 using CVSS 3.1 and 9.2/10 using CVSS 4.0, according to the advisories discussed by Sophos and Wiz. A high score does not mean every NGINX installation is exploitable: versions, modules and configurations determine actual exposure.

For CVE-2026-123007, hosting static content alone is not protection if NGINX accepts vulnerable HTTP/2 traffic. The other four vulnerabilities have additional technical requirements.

Five more vulnerabilities fixed in the same release

The official NGINX release history also lists CVE-2026-118899 (possible infinite loop when processing TLS 1.3 request bodies), CVE-2026-120993 (null-pointer dereference with PROXY protocol v2), CVE-2026-125283 (buffer overflow in certain alias/try_files configurations), CVE-2026-120967 (client-certificate validation bypass under specific SNI conditions), and CVE-2026-123640 (insufficient validation in stream ssl_preread).

These involve denial-of-service, authentication or routing issues and, under unusual configurations, memory corruption. The patching program should not stop at the two HTTP/2 CVEs.

Patched versions: upstream releases versus distribution packages

Product Affected upstream versions Fixed upstream version
NGINX Open Source stable 1.30.6 and applicable earlier versions 1.30.7 or later
NGINX Open Source mainline Up to 1.31.8, depending on the CVE 1.31.9 or later
NGINX Plus Selected releases across R33–R37 Branch-specific supported fixes

For NGINX Plus, relevant fixed builds include 37.0.8.1 and 37.3.0.1 depending on the branch and issue. Always refer to the F5 security bulletin for the exact product rather than applying Open Source numbering.

An older displayed upstream version does not necessarily mean a supported distribution package is vulnerable. Linux vendors can backport patches while retaining older upstream numbers. Validate the complete package version and its security advisory.

Ubuntu: fixed packages published 19 November 2026

Canonical published USN-9159-1, which lists these fixed official package versions:

Ubuntu version Fixed NGINX package
26.04 LTS 1.28.3-2ubuntu1.13
24.04 LTS 1.24.0-2ubuntu7.20
22.04 LTS 1.18.0-6ubuntu14.23

These versions apply to official Ubuntu packages, not NGINX from nginx.org, a third-party repository, a hand-built binary or a container image.

Debian: consult the security tracker before claiming a fix

On 19 November 2026, the Debian Security Tracker for CVE-2026-123007 still marked the listed Bookworm (Debian 12) and Trixie (Debian 13) packages as vulnerable, while Sid had a fixed 1.30.6-4 package.

This status can change quickly. Check the exact package version and repository, along with Debian's security notices. Having no packages left to upgrade does not prove that the necessary fix is available in the configured repository.

Practical NGINX checks on Linux

1. Inspect the compiled and installed versions

On servers using Debian/Ubuntu packages:

nginx -v
nginx -V 2>&1
dpkg-query -W 'nginx*'
apt-cache policy nginx nginx-core

nginx -v gives the compiled upstream version; the package queries identify complete distribution versions and package origins. Compare with the appropriate vendor advisory.

2. Review HTTP/2, HTTP/3 and other relevant settings

A preliminary search of the active configuration is:

sudo nginx -T 2>/dev/null | grep -nEi 'http2|quic|http3|resolver|proxy_pass|mirror|auth_http|ssl_preread'

The unfiltered nginx -T command prints all configuration and can reveal sensitive paths, hostnames and credentials. Do not post complete configuration output to public tickets or unauthorized services. A text search is only a starting point; review included files and the configuration NGINX has actually loaded.

If NGINX sits behind a CDN or load balancer, establish where HTTP/2 terminates. The visitor may use HTTP/2 to the CDN while the origin receives HTTP/1.1, or the architecture may differ across routes. CDNs and WAFs can limit some exposure but are not a replacement for patching.

3. Inspect Docker and Kubernetes deployments independently

NGINX may be embedded in Docker images, products such as OpenResty, or Kubernetes ingress controllers. The host's installed NGINX package does not prove the container image is patched.

docker ps --format '{{.Names}}  {{.Image}}'
docker exec CONTAINER_NAME nginx -v

# Adjust namespace, pod and container
kubectl exec -n NAMESPACE POD -c CONTAINER -- nginx -v

Inventory image tags, digests and publishers, then verify the versions on all running instances and any vendor-specific patched builds.

Temporary mitigation: disabling HTTP/2 and its limits

CERT-FR recommends disabling HTTP/2 when an immediate patch is not possible, to reduce exposure to CVE-2026-123007 and CVE-2026-123633.

For more recent configurations (NGINX 1.25.1 or later) supporting the dedicated directive:

server {
    listen 443 ssl;
    http2 off;
    # remaining configuration
}

For older versions, remove the http2 parameter from applicable listen directives: the standalone http2 off directive may not be supported. Review all relevant server blocks, test the configuration and reload:

sudo nginx -t && sudo systemctl reload nginx

Confirm HTTP/2 is no longer negotiated at the actual origin. A request to the public hostname may only describe the CDN's connection, not NGINX:

openssl s_client -connect example.com:443 -servername example.com -alpn h2 </dev/null 2>/dev/null | grep -F 'ALPN protocol'

If HTTP/3/QUIC is enabled, temporarily disabling it can reduce the specific exposure to CVE-2026-121810. These protocol changes do not necessarily mitigate resolver or mail proxy flaws, nor the additional five vulnerabilities fixed on 18 November. They are temporary measures only.

Upgrade, restart and verify running workers

On Ubuntu systems whose official repositories contain the patched packages:

sudo apt update
apt-cache policy nginx
sudo apt install --only-upgrade nginx
sudo nginx -t
sudo systemctl restart nginx
sudo systemctl status nginx --no-pager

Depending on the package variant, nginx-core, nginx-full or nginx-extras and their dependencies may also need updated builds. For containers, publish or obtain patched images and digests, then replace all running instances.

Installing fixed files on disk does not guarantee that obsolete NGINX worker processes have exited. On high-availability systems, perform a controlled rollout, validate application routes and confirm the version running on each node.

Incident response: evidence and limitations

CERT-EU suggests reviewing unexpected NGINX worker crashes, while warning that they are not reliable proof of code execution. Unrelated software errors can crash workers, and a successful exploit might not leave a visible crash.

An authorized investigation should correlate exposure timelines, actually running NGINX versions, HTTP/2 and HTTP/3 listener history, system and error logs, unusual processes spawned by NGINX, unexpected outbound traffic and suspicious file modifications. Preserve relevant timestamps, logs, configurations and forensic artifacts before destructive remediation.

Rapid7's demonstration involves a substantial amount of HTTP/2 traffic and specific technical prerequisites. These characterize that proof of concept, not necessarily all future exploitation approaches.

The operational lesson

A single edge proxy may serve many applications, making it a critical shared dependency. Security programs should inventory NGINX versions, protocol configurations, backported distribution packages, embedded runtimes, origin access and the ability to deploy patched images quickly.

GLOV Consulting describes GLOV Solutions' digital risk-management activities. For technically distinct cases, see our articles on Java4Shell and embedded JVMs, PHP2Shell reaching ESXi systems, and GPUStack behind a reverse proxy.

Information reviewed 19 November 2026. GLOV AI and digital forensics are still described as upcoming activities on the website. This article does not allege that GLOV Solutions or its customers were compromised.

Official sources and independent technical research

Related articles

Back to all articles