Five Critical Vulnerabilities Discovered in NGINX: A Threat to the World’s Most Popular Web Server
In a troubling development for web security, multiple research teams have independently identified five critical vulnerabilities in NGINX, the leading open-source web server that supports over 225 million websites globally. These vulnerabilities present a significant risk as they could potentially allow malicious actors to gain remote control over NGINX-hosted sites without requiring authentication.
On November 18, a consortium of security researchers from notable organizations including Wiz, which is owned by Google Cloud, Ikotas Labs, Metnir, Rapid7, and Xint, came forward with their discoveries related to NGINX version 1.31.8, which is the current release at the time. The vulnerabilities, labeled under the CVE identifiers CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634, all received high severity ratings of 9.2 according to the Common Vulnerability Scoring System (CVSS 4.0).
Interestingly, the disclosures varied among the research teams. Ikotas Labs highlighted one specific vulnerability known as "NGINX2Shell," while Wiz detailed two distinct vulnerabilities, specifically CVE-2026-123007 and CVE-2026-123633. Xint, on the other hand, documented a comprehensive set of five vulnerabilities, collectively titled "NGINX2Root," which underscores the substantial risk posed by these flaws.
Some researchers have publicly stated that they utilized artificial intelligence models and collaborated with OpenAI to aid in their search for these vulnerabilities, showcasing the innovative approaches being applied in the security landscape.
Vulnerabilities Detailed by Wiz: CVE-2026-123633 and CVE-2026-123007
Wiz’s report provides substantial detail on two of the critical vulnerabilities. CVE-2026-123633 is identified as a "use-after-free" vulnerability that could lead to memory corruption, while CVE-2026-123007 is related to an integer underflow in HTTP/2 flow control. Both vulnerabilities expose the vulnerability of NGINX servers by allowing unauthorized attackers to execute arbitrary code on affected systems remotely.
Wiz highlights the extensive scope of these vulnerabilities, indicating that they impact a wide range of NGINX versions. Alarmingly, one of the flaws dates back to 2015 and the other to 2020, meaning that many installations may be at risk. Exploitation of these vulnerabilities necessitates the enabling of HTTP/2, leading to recommendations for administrators to take immediate action.
In response, Wiz reported these serious flaws to F5, the organization responsible for maintaining NGINX. In timely fashion, F5 addressed these vulnerabilities in the updated versions of NGINX: 1.30.7 (stable) and 1.31.9 (mainline). For those unable to deploy updates right away, they advise disabling HTTP/2 until patches can be effectively implemented.
Xint’s Contributions: CVE-2026-113425, CVE-2026-121810, and CVE-2026-123634
Expanding on Wiz’s findings, Xint offered additional insights into three further NGINX vulnerabilities as part of their NGINX2Root research initiative. The vulnerabilities are as follows:
-
CVE-2026-123634: This vulnerability affects NGINX configurations that utilize the resolver, proxy_pass, and mirror directives, particularly when mirror_request_body is turned off. It opens up a pathway for attackers to exploit existing memory-handling issues within the request-processing flow.
-
CVE-2026-121810: This vulnerability arises in NGINX servers that employ HTTP/3 (QUIC) in conjunction with upstream proxy connections, including configurations that utilize proxy_pass, fastcgi_pass, or grpc_pass. This creates another potential attack route that could lead to remote code execution.
- CVE-2026-113425: Specifically impacting NGINX Mail Proxy deployments that utilize the proxy and auth_http directives, this vulnerability introduces a separate avenue for attackers to exploit the server.
All three of these vulnerabilities have been addressed by NGINX’s recent 1.31.9 release, though the organization cautions administrators and operators to review specific advisories for appropriate configuration-specific mitigations.
Xint reported that each of the five vulnerabilities has a demonstrable exploit, although the specific configurations and versions impacted vary. The firm also mentioned that, while they found no evidence of active exploitation in the wild as of the publication date, the historical age of some vulnerabilities prevents the possibility from being entirely ruled out.
The disclosed vulnerabilities are now listed across several CVE databases, including OpenCVE and CVE.org, heightening the urgency for website administrators to assess their NGINX installations and implement the necessary fixes.

