F5 Patches Five Critical NGINX Vulnerabilities Dubbed 'NGINX2Root'
F5 has released patches for five critical vulnerabilities in NGINX, collectively named NGINX2Root, with two allowing for remote code execution under specific circumstances.

F5 has released security updates to address five critical vulnerabilities discovered in NGINX, the widely-used open-source web server. These flaws, collectively dubbed "NGINX2Root" by researchers at Xint, pose a significant risk, as two of them, CVE-2026-123633 and CVE-2026-123007, can potentially lead to remote code execution (RCE) under specific conditions.
While there is currently no evidence of these vulnerabilities being exploited in the wild, and they have not yet been added to CISA's Known Exploited Vulnerabilities (KEV) catalog, the threat landscape is dynamic. Notably, a public proof-of-concept exploit for CVE-2026-123007 has already been made available, increasing the urgency for organizations to apply the patches.
NGINX serves a multitude of roles beyond being a web server, including acting as a reverse proxy, load balancer, mail proxy, and cache. The "NGINX2Root" vulnerabilities are: CVE-2026-123007 (an integer underflow in HTTP/2 flow control leading to heap out-of-bounds read/write, potentially causing crashes and RCE), CVE-2026-123633 (a use-after-free when HTTP/2 is used and requests are forwarded), CVE-2026-123634 (a use-after-free in the DNS resolver triggered by specific directive combinations), CVE-2026-121810 (a use-after-free from closing a QUIC connection during an HTTP/3 request), and CVE-2026-113425 (a use-after-free in the mail proxy's auth_http path).
Successful exploitation of any of these five vulnerabilities could allow for remote code execution with the privileges of the NGINX worker process, provided that address space layout randomization (ASLR) is disabled or bypassed. To achieve full system compromise and gain root privileges, attackers would need to chain these vulnerabilities with a sixth flaw. Researchers from Xint identified such a flaw in the Linux kernel's SCTP code, a use-after-free that can escalate to a double free, enabling root access on cloud hosts and even within Docker containers. This Linux kernel vulnerability, however, does not yet have a CVE assigned and remains unpatched.
Researchers from Xint and Wiz have developed proof-of-concept exploits for the five NGINX vulnerabilities but have not yet released them publicly. However, Rapid7's Stephen Fewer has published a technical analysis and a proof-of-concept exploit for CVE-2026-123007. This exploit is described as constrained, requiring specific build configurations, a large volume of HTTP/2 traffic, and the ability to defeat ASLR by inferring heap addresses from server responses. It is also less likely to succeed against servers behind HTTP/2-terminating proxies or on slow connections.
F5 strongly recommends upgrading to fixed versions of NGINX, including NGINX Open Source versions 1.30.7 and 1.31.9, and NGINX Plus versions 37.0.8.1 and 37.3.0.1. These releases also address five additional NGINX vulnerabilities. It is crucial for administrators to restart NGINX after applying updates, as a configuration reload is insufficient to replace the running executable. For users relying on distribution packages, checking for backported fixes is advised.
Beyond NGINX Open Source and Plus, these vulnerabilities may affect other F5 products such as NGINX Instance Manager, NGINX Ingress Controller, and NGINX Gateway Fabric. F5 has issued updates for some of these products and is actively working on patching the remaining ones. Xint researchers have also provided guidance for investigating potential attacks related to CVE-2026-123007.
Given the potential for widespread impact and the ongoing "vulnocalypse," organizations should prioritize automated patching, minimize internet-facing systems, and implement strict access controls to limit the potential damage from such vulnerabilities. The discovery and patching of the NGINX2Root vulnerabilities underscore the continuous need for vigilance and proactive security measures in managing critical web infrastructure.
The newly released article provides further technical details on the NGINX2Root vulnerabilities, including specific CVEs and how they can be exploited. It highlights that CVE-2026-113425 affects mail proxy configurations, while CVE-2026-121810 and CVE-2026-123633 involve use-after-free conditions in HTTP/2 or worker processes. Additionally, it notes that proof-of-concept exploits have been published, with one requiring significant traffic volume, while others have been demonstrated to bypass ASLR and achieve code execution even on servers serving static files.
The Tenable blog post provides a more detailed FAQ-style breakdown of the NGINX2Root vulnerabilities, including specific CVEs, their CVSSv4 scores, and the affected NGINX modules. It highlights CVE-2026-123007 as the most urgent due to its reliance on HTTP/2 and notes the existence of a public proof-of-concept exploit, while also clarifying that there is no evidence of these specific NGINX flaws being exploited in the wild as zero-days.