F5 has released security updates to address five critical vulnerabilities within the NGINX web server, a collection of flaws collectively identified by researchers at Xint as NGINX2Root. These vulnerabilities, which primarily affect the handling of HTTP/2 and other core protocols, could potentially allow for remote code execution under specific conditions. While the vulnerabilities are considered severe, F5 has confirmed there is currently no evidence of exploitation in the wild, and none of the issues are listed on the CISA Known Exploited Vulnerabilities catalog.
The five vulnerabilities include CVE-2026-123007, an integer underflow in HTTP/2 flow control that can result in out-of-bounds heap memory access, and CVE-2026-123633, a use-after-free condition triggered during HTTP/2 request forwarding to upstream servers. Additionally, CVE-2026-123634 involves a use-after-free in the NGINX DNS resolver, specifically when used in conjunction with certain proxy and mirror directives. The remaining two flaws are CVE-2026-121810, a use-after-free occurring when a QUIC connection is closed during an active HTTP/3 request, and CVE-2026-113425, a use-after-free located in the mail proxy’s authentication path.
Researchers from Xint, Rapid7, Wiz, Ikotas Labs, Palo Alto Networks, and Metnir have all contributed to the identification and reporting of these flaws. While Xint and Wiz have developed proof-of-concept exploits for the vulnerabilities, they have not released them publicly. Conversely, a proof-of-concept for CVE-2026-123007, also referred to as NGINX2Shell, has been made public. Technical analysis indicates that this specific exploit is constrained by several factors, including a requirement for significant data volume—approximately 128 gigabytes of HTTP/2 traffic—and the need to bypass address space layout randomization (ASLR) by recovering heap addresses.
Beyond the NGINX-specific flaws, Xint researchers identified a separate, unpatched vulnerability in the Linux kernel’s SCTP implementation. This kernel-level issue, which currently lacks a CVE identifier, can be leveraged to escalate privileges from the NGINX worker process to root. Researchers successfully demonstrated this chain by gaining a root shell on the host system from within a Docker container. While the NGINX vulnerabilities allow for code execution at the level of the worker process, achieving full root access remains dependent on this additional kernel-level flaw.
F5 has addressed these issues in NGINX Open Source versions 1.30.7 and 1.31.9, as well as NGINX Plus versions 37.0.8.1 and 37.3.0.1. The company also implemented fixes for five additional, separate NGINX vulnerabilities within these same releases. Because a standard configuration reload does not replace the active binary, F5 advises administrators to perform a full restart of the NGINX service after applying the patches. Users relying on distribution-specific packages are encouraged to verify if backported fixes have been provided by their OS maintainers.
The vulnerabilities also impact other F5 products that incorporate NGINX, such as the NGINX Ingress Controller, NGINX Instance Manager, and NGINX Gateway Fabric. F5 has confirmed that updates for some of these products are available, while work on remaining components is ongoing.
Security experts suggest that given the complexity of patching large-scale infrastructure, organizations should prioritize the automation of update processes and minimize the number of internet-facing systems. Furthermore, implementing strict access controls to limit the resources available to individual applications can serve as a defense-in-depth measure against potential exploitation. Xint has provided guidance for administrators to investigate their environments for indicators of compromise related to CVE-2026-123007.



