A pair of critical flaws affecting NGINX, collectively branded "nginx2root," enable unauthenticated remote code execution on unpatched web servers. Security researchers from Xint, Wiz, Ikotas Labs, Metnir, and Rapid7 independently discovered these HTTP/2 vulnerabilities, with Xint additionally uncovering three more NGINX remote code execution issues. Censys later verified the memory corruption conditions underlying four of the five flaws through controlled testing, though the organization did not achieve remote code execution itself.

The Two Critical Flaws

image

The first vulnerability, designated CVE-2026-123007, stems from a flow-control defect that corrupts memory within an NGINX worker process. This flaw affects all versions spanning from 1.31.8 back through 1.9.5, released in 2015. Wiz demonstrated unauthenticated remote code execution against a server delivering standard static content via HTTP/2 with TLS encryption. Xint went further, chaining this vulnerability with a separate Linux kernel vulnerability to achieve root access by escaping an NGINX Docker container and gaining root privileges on the host system.

The Linux kernel vulnerability that Xint leveraged resides in the SCTP subsystem, allowing attackers to escalate privileges beyond the container environment.

https://www.youtube.com/embed/3hhN9fKEY7E

The second critical flaw, CVE-2026-123633, is a use-after-free vulnerability triggered when NGINX processes HTTP/2 connections and forwards requests to backend servers. This issue affects versions 1.19.7 through 1.31.8. When a worker exhausts available connection slots, it may terminate an active connection and deallocate memory that an in-flight request still references. Wiz also demonstrated remote code execution via this vulnerability but has opted not to publicly disclose its proof-of-concept exploit at present.

Additional Vulnerabilities Fixed

https://www.youtube.com/embed/6z3nvpxCiHM

Beyond the two primary flaws, researchers identified three additional use-after-free vulnerabilities that F5 has now patched: CVE-2026-121810, CVE-2026-123634, and CVE-2026-113425. These affect HTTP/3 reverse proxying, DNS resolution with subrequests, and mail proxy authentication respectively.

F5's security update addresses five additional vulnerabilities not featured in the Wiz or Xint disclosures. Among these, CVE-2026-118899 carries high severity and permits unauthenticated attackers to force a worker into an infinite loop while processing a request body over TLS 1.3, resulting in denial of service.

Patching and Mitigation

NGINX Open Source users should upgrade to version 1.30.7 stable or 1.31.9 mainline. NGINX Plus subscribers need to update to either 37.0.8.1 or 37.3.0.1. System administrators are advised to apply updates immediately, or as an interim measure, disable HTTP/2 until patching is feasible—though this mitigation only addresses the two "nginx2root" vulnerabilities.

Evaluating the Risk

Security researcher Florian Roth characterized the exploitability risk of "nginx2root" as exceeding that of Node2Shell and Java2Shell, yet cautioned that it does not represent an immediate threat for most NGINX installations. Roth noted on X that the flaws require non-default configurations, and that assertions of widespread exposure derived solely from NGINX version numbers are misleading.

Xint previously reported that 98.9% of NGINX hosts revealing identifiable versions fell within the affected range, but this statistic overlooks whether HTTP/2 is actually enabled or whether security patches have been backported into older versions.

Successful exploitation of the two HTTP/2 flaws requires an unpatched server with HTTP/2 enabled on a publicly accessible listener. CVE-2026-123633 additionally mandates that NGINX forward requests to a backend system. When Roth scanned a sample of several hundred NGINX HTTPS endpoints from Shodan, approximately 66% supported HTTP/2, but determining genuine exposure demands inspection of server configuration and verification of applied patches.

According to Censys' live exposure tracking, roughly 8.8 million NGINX services faced potential exposure to CVE-2026-123007 as of November 19, based on affected version numbers and HTTP/2 availability. Censys reports that more than 511,000 previously vulnerable services have since been patched or mitigated. An additional 104 million NGINX services do not reveal their version information, complicating efforts to assess whether they remain vulnerable.