More than 225 million websites worldwide rely on NGINX — and on November 18 a set of five newly disclosed critical flaws threatened many of them.
Scope: NGINX 1.31.8 and five critical CVEs (9.2/10)
Security researchers at Google Cloud-owned Wiz, Ikotas Labs, Metnir, Rapid7 and Xint publicly disclosed a group of vulnerabilities in NGINX 1.31.8, the current release. The disclosures name five CVEs: CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634. Each is listed with a critical severity rating of 9.2 under CVSS 4.0.
The source describes these flaws as capable of enabling unauthenticated, remote attackers to execute arbitrary code on vulnerable servers — a capability that, if realized, would allow attackers to take control of NGINX-based websites without authentication.
Wiz findings: CVE-2026-123633 (use‑after‑free) and CVE-2026-123007 (HTTP/2 integer underflow)
Wiz documented two of the five flaws. According to Wiz, CVE-2026-123633 is a use‑after‑free vulnerability that can cause memory corruption; CVE-2026-123007 is an integer underflow in HTTP/2 flow control. Wiz says both could allow unauthenticated remote code execution and that exploitation requires HTTP/2 to be enabled.
Wiz reported the flaws to F5, identified in the disclosures as the maintainer of NGINX. F5 addressed the two Wiz-reported vulnerabilities in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). Administrators unable to upgrade immediately were advised to disable HTTP/2 until patches can be applied.
Wiz also reported that the affected codepaths span a wide range of NGINX versions, with one vulnerability tracing back to 2015 and the other to 2020, indicating long-lived exposure in certain deployments.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleXint’s NGINX2Root: CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425
Xint’s research, released under the “NGINX2Root” name, adds three further critical vulnerabilities and provides configuration-specific details:
- CVAE-2026-123634 — affects configurations that use resolver, proxy_pass and mirror together with mirror_request_body off; it can enable exploitation of memory-handling flaws in the request-processing path.
- CVE-2026-121810 — affects servers using HTTP/3 (QUIC) with upstream proxy connections (including configurations using proxy_pass, fastcgi_pass or grpc_pass), creating another potential route to remote code execution.
- CVE-2026-113425 — affects NGINX Mail Proxy deployments that use the proxy and auth_http directives, opening a separate attack path.
All three of Xint’s additional vulnerabilities are addressed by the NGINX 1.31.9 release. Xint advised operators to consult the individual advisories for configuration-specific mitigations, reflecting that exploitation depends on specific directive combinations and deployment choices.
Research coordination, AI use, and exploit claims
The disclosures were coordinated across multiple research teams and differed in scope: Ikotas Labs highlighted a single vulnerability it named “NGINX2Shell,” Wiz detailed two, and Xint documented five under “NGINX2Root.” Some of the teams publicly disclosed they used AI models and collaborated with OpenAI in the process of finding vulnerabilities.
Xint stated that each of the five vulnerabilities has a proven exploit, though it also said it had no evidence of exploitation in the wild at the time of publication. Xint noted that the age of some vulnerabilities means exploitation cannot be ruled out. The CVEs are listed on public databases including OpenCVE and CVE.org.
What this means for administrators, enterprises, and end users
Administrators and security teams — The most immediate actions flagged in the reporting are to apply the patches provided (NGINX Open Source 1.30.7 for the Wiz fixes and 1.31.9 for the broader set) or, if an immediate upgrade is not feasible, to disable HTTP/2 until the fixes are applied. Operators running configurations that combine resolver, proxy_pass and mirror, or running HTTP/3 with upstream proxy connections, should consult the configuration-specific advisories to determine exposure.
Affected enterprises and procurement leaders — The disclosures underscore the need to inventory where NGINX is in use — including mail proxy deployments and upstream proxy configurations — and to coordinate patching across distributed environments. Because some affected codepaths date to 2015 and 2020, legacy deployments should be checked explicitly.
End users and the general public — The vulnerabilities enable remote code execution on affected servers, which can lead to full compromise of hosted sites. Xint reported no evidence of active exploitation at the time of disclosure, but also warned the age of some flaws keeps the risk open.
Multiple research teams, public CVE listings and patched releases converge on a single, practical imperative: where NGINX is deployed at scale, operators should treat these releases and configuration advisories as urgent. The fixes exist; the remaining question, precisely stated by the research, is how many live deployments combine the specific directives and protocol support (HTTP/2 or HTTP/3 with upstream proxies) that would allow a remote, unauthenticated attacker to translate these vulnerabilities into takeover.




