NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2
On November 18 2026 NGINX developers released fixes for ten vulnerabilities five of which researchers grouped under the name NGINX2Root. The most dangerous flaw CVE-2026-123007 allows remote command execution on servers with HTTP/2 enabled without any administrator password application access or site code errors. Attackers need only the ability to establish HTTP/2 connections to a vulnerable NGINX instance together with memory error conditions required for exploitation.
What is NGINX2Root and why the vulnerabilities are so dangerous
NGINX2Root is the name of research by the Xint team from Theori. Specialists found five independent errors in NGINX each of which under the right configuration can lead to memory corruption and remote code execution. Researchers also identified a sixth vulnerability in the Linux kernel that allows privilege escalation to root after initial access.
F5 rated all five web server flaws at 9.2 under CVSS 4.0 corresponding to critical severity and 8.1 under the previous CVSS 3.1 scale. The presence of vulnerable code does not mean every server can be immediately compromised because each error requires specific conditions and successful code execution also depends on process memory layout.
Which five vulnerabilities are included in NGINX2Root
Two errors relate to HTTP/2 one affects HTTP/3 and two reside in domain name resolution and mail proxy mechanisms. For CVE-2026-123007 it is sufficient that the server accepts HTTP/2 connections. The others require additional conditions such as request proxying lack of available connections or specific configuration directives.
- CVE-2026-123007 â Memory corruption due to HTTP/2 flow control management error. Requires HTTP/2 enabled. Affected versions 1.9.5â1.31.8.
- CVE-2026-123633 â Use-after-free when processing HTTP/2. Requires request proxying and connection exhaustion conditions. Affected versions 1.19.7â1.31.8.
- CVE-2026-121810 â Use-after-free when processing HTTP/3 over QUIC including connection closure due to resource exhaustion. Affected versions 1.25.0â1.31.8.
- CVE-2026-123634 â Use-after-free in the DNS resolver. Requires specific dynamic proxy configuration and additional requests. Affected versions 0.6.18â1.31.8.
- CVE-2026-113425 â Use-after-free in mail proxy during auth_http authentication. Affected versions 0.5.33â1.31.8.
How CVE-2026-123007 works from HTTP/2 to command execution
HTTP/2 allows multiple data streams over a single connection. NGINX reduces the available window counter when queuing response data. The flaw occurs when a client increases the window while data remains queued and then closes the stream. NGINX returns the reserved window without checking whether the final counter stays within valid limits leading to integer overflow and an oversized memcpy operation that corrupts adjacent memory.
Attackers can first bypass ASLR to obtain object addresses then corrupt a function pointer called during connection cleanup to execute arbitrary commands with the privileges of the NGINX worker process.
How attackers obtain root and escape Docker
Remote code execution via NGINX typically grants only unprivileged worker process rights such as nginx or www-data. Researchers found a separate Linux kernel vulnerability in the SCTP subsystem that appeared in Linux 4.15 in 2018. The flaw allows an SCTP association to be moved to another socket while a pending operation still references it resulting in use-after-free conditions.
The team demonstrated root privilege escalation from an NGINX worker process and container escape from Docker to the host. On systems where SCTP is unused administrators should prevent automatic module loading with the rule install sctp /bin/false placed in /etc/modprobe.d/.
Working exploits and ease of server compromise
Exploitation of CVE-2026-123007 has been confirmed by Wiz Rapid7 Xint Ikotas Labs and Metnir. Rapid7 published a working example on NGINX 1.31.8 in an amd64 Linux container that requires AVX-512F and AVX-512VL support plus approximately 128 GB of HTTP/2 traffic. Other teams demonstrated alternative exploitation paths that do not share these exact constraints.
Fixed NGINX versions
NGINX Open Source received versions 1.30.7 (stable) and 1.31.9 (mainline). NGINX Plus fixes appear in 37.0.8.1 and 37.3.0.1. Older R33âR36 branches require migration to a supported branch. Linux distributions may backport fixes without changing the main NGINX version number so administrators must verify full package versions.
How to check servers for NGINX2Root
Run nginx -v and nginx -V to identify the version and build parameters. Use sudo nginx -T to inspect the live configuration for http2 on listen directives quic http3 resolver proxy_pass mirror and auth_http. External HTTP/2 availability can be verified with openssl s_client using the alpn h2 parameter.
How to close the vulnerabilities and temporary mitigations
The most reliable fix is installation of patched versions followed by a full service restart because configuration reload alone does not replace running binaries. If immediate updates are impossible disable HTTP/2 with http2 off remove QUIC listeners replace dynamic proxy_pass with static upstream groups restrict mail proxy access and block SCTP module loading.
Related articles
F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway
Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.
Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4
China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.
Wireshark 4.6.10 Released with Fixes for 39 Vulnerabilities and Multiple Protocol Dissectors
The open-source network protocol analyzer Wireshark has received its 4.6.10 update, addressing 14 bugs along with 39 security vulnerabilities discovered during testing. The release continues the 4.6 development branch that began in October 2025 and follows the long-standing stable line that started with version 1.0.0 in 2008. Patches cover a wide range of protocol dissectors including RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU, ACN, PROFINET, SDP, MsgPack, NNTP, TLS, and SCTP. Additional corrections resolve infinite loops in the Kafka dissector and Tektronix K12xx file parser, heap disclosure issues, and a remote code execution flaw in LoRaWAN decryption tracked as ZDI-CAN-32851. The update also ships Npcap 1.89 for Windows installers and changes the default extcap directory on Unix-like systems to libexec for better multiarch compatibility.
Critical Authentication Bypass Zero-Day in VMware vCenter Exploited Since September
Broadcom disclosed a critical authentication bypass vulnerability in VMware vCenter that has been actively exploited in the wild since at least early September 2026. The flaw, tracked as CVE-2026-123890, resides in the product's directory service and carries a CVSSv3.1 base score of 9.8. Mandiant, in collaboration with Google Threat Intelligence Group, confirmed that threat actors began weaponizing the issue months before the November 19, 2026 advisory. Broadcom also addressed four additional vulnerabilities affecting SDDC Manager and VMware Tools, including SQL injection, command injection, and local privilege escalation flaws. The company rated the overall advisory as Critical and urged immediate patching.