A collection of five security vulnerabilities, collectively dubbed NGINX2Root, was disclosed on November 18, 2026, affecting various versions of NGINX Open Source and NGINX Plus. The most severe of these, CVE-2026-123007, is a memory corruption flaw within the server’s HTTP/2 implementation. F5, the maintainer of NGINX, has assigned this lead vulnerability a CVSS v4.0 score of 9.2.
The vulnerability stems from how NGINX manages HTTP/2 data allowances. When a client cancels requests at specific intervals, the server can experience a counting error, leading it to copy data into unauthorized memory regions. While the primary result of this flaw is a crash of the NGINX worker process, researchers have demonstrated that remote code execution is possible if memory address randomization protections are bypassed.
The scope of the vulnerability includes NGINX Open Source versions 1.9.5 through 1.31.8, as well as specific builds of NGINX Plus. Systems are only considered vulnerable if they have HTTP/2 enabled. While F5 has released patches in NGINX Open Source versions 1.30.7 and 1.31.9 to address these issues, organizations unable to patch immediately can mitigate the risk by disabling the HTTP/2 module.
Beyond the primary memory corruption bug, NGINX2Root encompasses four additional vulnerabilities, all sharing the same severity scores as the lead flaw. These include issues related to specific proxy configurations, HTTP/3 enablement, and mail proxy functionality. Each of these requires distinct configuration conditions to be exploitable, and unlike the primary flaw, some cannot be mitigated simply by disabling HTTP/2.
Researchers have confirmed that the NGINX worker process typically runs with restricted privileges. However, they successfully chained the primary NGINX vulnerability with an unpatched local privilege-escalation flaw in the Linux kernel’s SCTP code to achieve root access on the host machine. This escalation path remains a concern even after the NGINX software is patched, as the underlying kernel vulnerability currently lacks a fix.
The potential impact of a successful exploit is significant. An attacker gaining code execution within an NGINX worker process could potentially intercept decrypted traffic, including sensitive session tokens, passwords, and TLS private keys. Furthermore, because NGINX often acts as a reverse proxy or load balancer, a compromised instance provides a foothold into the internal network, potentially bypassing perimeter defenses.
As of the disclosure date, there have been no confirmed reports of these vulnerabilities being exploited in the wild. However, functional exploit code has been made public. Researchers noted that the current exploit requires a sustained, multi-minute stream of HTTP/2 control messages and is dependent on specific memory-copy routines found in standard Linux C libraries on 64-bit Intel and AMD architectures. While these technical requirements may hinder mass exploitation, they do not preclude targeted attacks against internet-facing infrastructure.
Organizations are advised to verify their exposure by checking both the NGINX build version and the active configuration. Relying solely on version numbers is discouraged, as many Linux distributions apply backported security fixes without incrementing the primary version string. Administrators should inspect configuration files for active HTTP/2 listeners and perform external testing using tools like OpenSSL to confirm if the ALPN protocol is negotiating h2.
The status of bundled NGINX instances varies. While some official Docker images and F5-maintained ingress controllers have been updated, other third-party products and community-maintained projects may remain vulnerable. Notably, the community-led Ingress-NGINX for Kubernetes project, which was archived earlier in 2026, will not receive security updates for these flaws. F5 has confirmed that its BIG-IP, BIG-IQ, and F5OS products are not affected by these vulnerabilities.



