F5 on Wednesday announced patches for 22 vulnerabilities, including five critical-severity NGINX bugs that could lead to unauthenticated remote code execution (RCE). Referred to as NGINX2Root, the five issues are tracked as CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634 (CVSS score of 9.2). CVE-2026-113425 affects NGINX instances configured as mail proxy servers and can be exploited […]
F5 on Wednesday announced patches for 22 vulnerabilities, including five critical-severity NGINX bugs that could lead to unauthenticated remote code execution (RCE).
Referred to as NGINX2Root, the five issues are tracked as CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634 (CVSS score of 9.2).
CVE-2026-113425 affects NGINX instances configured as mail proxy servers and can be exploited via specially crafted mail sessions. CVE-2026-121810 can be exploited on servers that use HTTP/3 to trigger a use-after-free in the NGINX worker process.
CVE-2026-123634 impacts servers configured as proxies and can be triggered if the proxied server name includes variables, and a subrequest to a location resolving that server name is received from a Server Side Includes (SSI) or mirror directive.
CVE-2026-123007 and CVE-2026-123633 require HTTP/2 to be enabled on an affected server. Successful exploitation of the former leads to a buffer overflow, while the latter triggers a use-after-free in the worker process.
The two issues were independently reported by Ikotas Labs, Metnir, Rapid7, Wiz, and Xint. They explain that attackers could exploit them to run commands with the privileges of the nginx worker process and fully compromise the server.
Advertisement. Scroll to continue reading.
“Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules,” Wiz explains, noting that the flaw affects all NGINX iterations since 1.9.5 (released in 2015).
Xint says it chained CVE-2026-123007 with a Linux kernel vulnerability to escape a Docker container and gain root privileges on the underlying host.
According to F5, code execution is only possible if ASLR is disabled or bypassed. However, Wiz says CVE-2026-123007 and CVE-2026-123633 can themselves be used to bypass ASLR, and Rapid7’s public exploit defeats the protection by leaking memory addresses from server responses.
PoC code available
Rapid7 has published proof-of-concept (PoC) code targeting CVE-2026-123007, but warns that successful exploitation for RCE requires “a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data.”
Depending on network bandwidth and connection timeouts, exploitation could take between two minutes and one hour. On slow connections, NGINX’s default one-hour connection lifetime prevents exploitation.
“Additionally, should an HTTP/2 connection be proxied, the precise attacker-controlled HTTP/2 frames being transmitted will likely not be retransmitted in a way that satisfies exploiting the vulnerability,” Rapid7 notes.
Internet intelligence provider Censys says it tested the NGINX2Root flaws in its lab and was able to reproduce CVE-2026-123007’s behavior using cleartext HTTP/2 without generating the large traffic volume reported by Rapid7.
Censys published its PoC on GitHub, warning that there are approximately 9 million “NGINX services on an affected version with HTTP/2 on” and that 103 million additional services do not reveal their version.
F5 patches
F5 resolved the vulnerabilities in NGINX Open Source versions 1.30.7 and 1.31.9, and in NGINX Plus versions 37.0.8.1 and 37.3.0.1.
The updates also include patches for five flaws that can lead to SSL/TLS connection termination, certificate verification bypass, segmentation faults, worker process termination, and denial-of-service (DoS) by placing the worker process in an infinite loop.
Additionally, the company rolled out patches for 12 BIG-IP bugs, including critical and high-severity issues that could lead to RCE, DoS, file manipulation, and token lifetime manipulation.
F5 makes no mention of any of these vulnerabilities being exploited in the wild. More information is available in the company’s out-of-band security notification.
Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw
Related: Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories
