Critical Security 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, NGINX is a fundamental pillar of the modern internet infrastructure, making the discovery of these flaws a significant concern for web administrators, cloud architects, and security professionals worldwide. The vulnerabilities, which carry a severe CVSS 4.0 rating of 9.2, could potentially allow unauthenticated remote attackers to gain unauthorized control over affected servers, posing a substantial risk to data integrity and system availability.
The coordinated disclosure took place on November 18, involving a diverse group of security organizations including Wiz, Ikotas Labs, Metnir, Rapid7, and Xint. These entities collectively identified several flaws within NGINX version 1.31.8, the current release at the time of discovery. The findings have been cataloged under five distinct Common Vulnerabilities and Exposures (CVE) identifiers: CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634.
While the severity rating across these flaws is consistently high, the reporting approach among the researchers has varied, leading to different classifications of the security threat. Ikotas Labs has focused its attention on a singular, high-impact vulnerability it has dubbed “NGINX2Shell.” Meanwhile, researchers at Wiz have provided a detailed analysis of two specific vulnerabilities—CVE-2026-123007 and CVE-2026-123633—which they have scrutinized for their potential impact on HTTP/2 implementations. In a broader assessment, Xint has documented the entire suite of five vulnerabilities, categorizing them under the collective moniker “NGINX2Root.”
A notable aspect of this discovery is the methodology employed by the research teams. Several organizations involved in the disclosure have publicly acknowledged the use of advanced AI models in their research process. Specifically, some teams collaborated with OpenAI to streamline the identification and analysis of these vulnerabilities. This integration of artificial intelligence into the vulnerability research lifecycle underscores a growing trend in the cybersecurity industry, where machine learning is being utilized to identify complex code flaws that might otherwise remain undetected by traditional manual auditing methods.
Wiz Report: Analysis of CVE-2026-123633 and CVE-2026-123007
The technical findings presented by Wiz provide a clear window into the nature of the risks posed to NGINX users. CVE-2026-123633 has been identified as a use-after-free vulnerability. In technical terms, this occurs when an application continues to use a pointer to a memory location after that memory has been freed or reallocated. This type of memory corruption can be weaponized by an attacker to manipulate the program’s execution flow, potentially leading to the remote execution of arbitrary code with the privileges of the NGINX process.
Parallel to this, CVE-2026-123007 involves an integer underflow vulnerability specifically related to the HTTP/2 flow control mechanism. An integer underflow occurs when an arithmetic operation attempts to create a numeric value that is smaller than the minimum representable value for that data type. In the context of NGINX’s HTTP/2 implementation, this flaw could be exploited to bypass security checks or crash the service, eventually allowing an attacker to inject and execute malicious code.
According to Wiz’s analysis, both of these vulnerabilities affect a surprisingly broad spectrum of NGINX versions, with the origins of the flaws dating back to 2015 and 2020, respectively. This longevity highlights the persistent nature of security debt in widely used software. A critical prerequisite for the exploitation of these two flaws is that the target server must have HTTP/2 support enabled. For organizations currently unable to undergo an immediate software upgrade, Wiz has recommended the temporary disabling of HTTP/2 as a functional, albeit limited, mitigation strategy until patches can be successfully deployed.
The researchers at Wiz proactively reported these findings to F5, the organization responsible for the ongoing maintenance and development of NGINX. In response, F5 has released security updates for both the stable and mainline versions of the software. Users are urged to upgrade to NGINX Open Source 1.30.7 for the stable branch or 1.31.9 for the mainline branch to ensure these specific vulnerabilities are mitigated.
Xint’s Analysis of the NGINX2Root Vulnerabilities
While Wiz’s reporting focused on the HTTP/2-related flaws, the research collective known as Xint has expanded the scope of the conversation by documenting three additional vulnerabilities: CVE-2026-113425, CVE-2026-121810, and CVE-2026-123634. These flaws form the remainder of the five-part “NGINX2Root” disclosure. Like the vulnerabilities identified by Wiz, these additional issues are addressed in the latest NGINX 1.31.9 release.
Xint has emphasized that while the vulnerabilities represent a significant threat, the specific requirements for exploitation vary depending on the target system’s configuration. This complexity means that a "one-size-fits-all" approach to threat modeling may not be sufficient for security teams. Instead, administrators are encouraged to consult the detailed technical advisories provided by Xint and other researchers to understand the configuration-specific risks unique to their own environments.
A point of concern raised by Xint is the existence of functional exploits for all five vulnerabilities. Although the researchers have confirmed that they have not observed evidence of these exploits being used in the wild at the time of the initial disclosure, the age of some of the underlying vulnerabilities—some of which have existed in the codebase for years—means that the security community cannot rule out the possibility that they have already been identified and leveraged by malicious actors. The possibility that these flaws have been known in private circles before this public disclosure necessitates a prompt and prioritized response from IT departments globally.
The CVE identifiers for these vulnerabilities have been officially registered and are now being listed on major industry databases, including OpenCVE and CVE.org. This standardization ensures that automated vulnerability scanners and security information and event management (SIEM) systems can now detect and flag vulnerable NGINX installations, allowing for more efficient remediation efforts.
The rapid identification and disclosure of these five vulnerabilities highlight the critical importance of ongoing security research in the open-source ecosystem. As NGINX continues to serve as the backbone for a significant portion of the global web, the collaborative effort between security firms like Wiz, Ikotas Labs, Metnir, Rapid7, and Xint—bolstered by the power of AI—serves as a vital line of defense. For administrators, the path forward is clear: review the latest release notes from F5, assess current infrastructure configurations, and apply the necessary patches to protect against these critical risks. Failure to address these vulnerabilities could leave organizations exposed to remote attacks, emphasizing the necessity of maintaining updated software in an increasingly complex and hostile threat landscape.
| Source | : | Finance Poetry |
| Author | : | rifanmuazin |
| Editor | : | Finance Poetry Editorial Team |
