Five Critical Vulnerabilities Discovered in NGINX Web Server: Urgent Patching Required

A coalition of leading security research firms has unveiled a series of five critical vulnerabilities affecting NGINX, the world’s most widely deployed open-source web server. Powering more than 225 million websites globally—ranging from small personal blogs to the infrastructure of some of the world’s largest technology companies—NGINX serves as the backbone of the modern internet. The discovery of these flaws, which could allow unauthenticated remote attackers to gain full control over affected systems, has sent a wave of concern through the cybersecurity community and prompted immediate calls for global software updates.

The disclosure, which occurred on November 18, involved a coordinated effort by several prominent security organizations, including Google Cloud-owned Wiz, Ikotas Labs, Metnir, Rapid7, and Xint. The vulnerabilities, identified as CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634, have all been assigned a critical severity rating of 9.2 on the CVSS 4.0 scale. This high-risk classification highlights the severity of the flaws, as they could potentially allow unauthorized actors to execute arbitrary code on servers without requiring any prior authentication.

Disparate Disclosures and Research Collaboration

While the research community is unified in the assessment of the severity of these vulnerabilities, the specific reporting and naming conventions differ significantly between the teams involved. Ikotas Labs has focused its attention on a singular, high-impact vulnerability it has dubbed "NGINX2Shell." In contrast, the researchers at Wiz have provided a detailed analysis of two specific flaws: CVE-2026-123007 and CVE-2026-123633. Meanwhile, the security firm Xint has taken a more comprehensive approach, documenting all five vulnerabilities under a collective moniker they refer to as "NGINX2Root."

The discovery of these vulnerabilities is particularly notable for the methodology employed by the research teams. Several of these organizations have publicly acknowledged that they utilized advanced artificial intelligence models to assist in the identification of these flaws, even collaborating with OpenAI during the research process. This development underscores an evolving landscape in cybersecurity, where AI is increasingly being leveraged not only by attackers but also by defenders to uncover complex, long-standing security gaps in foundational software.

Detailed Analysis of the HTTP/2 Vulnerabilities

The research provided by Wiz offers critical insight into two of the five identified vulnerabilities: CVE-2026-123633 and CVE-2026-123007. According to their findings, CVE-2026-123633 is a "use-after-free" vulnerability that can lead to significant memory corruption. In software engineering, a use-after-free error occurs when an application continues to use a pointer to a memory location after that memory has been freed, a scenario that attackers can manipulate to execute malicious code.

The second flaw highlighted by Wiz, CVE-2026-123007, involves an integer underflow occurring within the HTTP/2 flow control mechanism. Like the former, this vulnerability provides a potential pathway for unauthenticated remote code execution. Wiz noted that these vulnerabilities affect a surprisingly wide range of NGINX versions, with some of the underlying code flaws dating back to 2015 and 2020. A key prerequisite for the exploitation of these two specific vulnerabilities is that the server must have HTTP/2 enabled, which is a common configuration for modern high-performance web servers.

F5, the company that maintains the NGINX project, was notified by the research teams prior to public disclosure. In response, F5 has released patches to address these vulnerabilities in NGINX Open Source version 1.30.7 for the stable branch and 1.31.9 for the mainline branch. For organizations and administrators who find themselves unable to perform an immediate upgrade to their server infrastructure, security experts strongly advise the temporary disabling of the HTTP/2 protocol as an effective stopgap measure to mitigate the risk until a patch can be successfully applied.

Broader Scope: The NGINX2Root Findings

The research conducted by Xint expands the scope of the threat beyond the two vulnerabilities analyzed by Wiz. By documenting CVE-2026-113425, CVE-2026-121810, and CVE-2026-123634, Xint has provided a more holistic view of the vulnerabilities that exist within the NGINX codebase. While all five of these critical vulnerabilities are addressed by the latest NGINX 1.31.9 release, the variety of the bugs suggests that the attack surface of the software is more complex than previously understood.

Xint has stated that they have developed a proven exploit for each of the five vulnerabilities. While they have clarified that the specific configuration requirements and the versions affected vary from one vulnerability to another, the presence of functional exploits is a major cause for concern. Operators are urged to consult the individual technical advisories provided by the researchers and the software maintainers, as certain mitigations may be specific to particular server configurations.

The security company emphasized that, at the time of their publication, there was no concrete evidence suggesting that these vulnerabilities were being exploited "in the wild" by malicious actors. However, they provided a stark warning: given that some of these vulnerabilities have existed within the NGINX source code for several years, the possibility that they may have been discovered and utilized by sophisticated attackers prior to this public disclosure cannot be entirely ruled out.

The importance of these vulnerabilities is reflected in their inclusion across multiple authoritative security databases, including OpenCVE and CVE.org. The breadth of this incident—spanning multiple researchers, a high volume of affected installations, and the potential for total remote control—marks this as one of the most significant security events for web server infrastructure in recent years. As administrators begin the task of auditing their environments and applying the necessary patches, the incident serves as a reminder of the inherent risks associated with the core software that maintains the integrity of the modern digital economy. Users of NGINX are encouraged to prioritize these updates in their regular maintenance cycles, as the combination of public exploitability and widespread adoption makes these systems prime targets for potential future campaigns.