A recent report indicates that approximately 8.8 million NGINX services remain vulnerable to the NGINX2Root security threats. According to live data from Censys, 8,823,450 services are operating on affected versions that support HTTP/2. Meanwhile, 441,489 services have either been updated or have disabled HTTP/2 to mitigate these risks.
Understanding NGINX2Root Vulnerabilities
The NGINX2Root vulnerabilities encompass five distinct memory-related flaws disclosed by security firm Xint on November 18, 2026. These vulnerabilities lie within the NGINX worker process and require specific configurations to be exploited. Xint warns that an unauthenticated attacker could potentially execute commands remotely via these flaws.
The most critical of these vulnerabilities, CVE-2026-123007, impacts all official releases from versions 1.9.5 to 1.31.8, a timeframe dating back to the introduction of HTTP/2 in 2015. Xint further combined this with a Linux kernel vulnerability within the SCTP subsystem to achieve root access, even breaching Docker container isolation.
Details of the Vulnerability Setup
Censys’ advisory highlights that different configurations are required for each of the five vulnerabilities. For instance, CVE-2026-123007 only necessitates HTTP/2, while CVE-2026-123633 requires a backend proxy. Other vulnerabilities demand HTTP/3, DNS lookups, or specific mail proxy configurations.
Despite HTTP/2 deactivation addressing two vulnerabilities, systems using HTTP/3, mail proxies, or runtime DNS configurations remain susceptible until updated. Notably, F5 has rated all five vulnerabilities as high risk, scoring them 8.1 on CVSS v3.1 and 9.2 on CVSS v4.0.
Mitigation and Future Outlook
To mitigate the vulnerabilities, it is advised to upgrade NGINX Open Source to version 1.30.7 or later on the stable branch, or to 1.31.9 or newer on the mainline branch. NGINX Plus users should update to versions 37.0.8.1 or 37.3.0.1. It’s crucial to restart services post-update, as simple reloads do not replace the active binary.
In cases where immediate patching is unavailable, disabling HTTP/2 and HTTP/3, and securing mail proxies from untrusted access, are recommended interim measures. As of November 18, Censys reported no active exploitation in the wild, and these vulnerabilities have yet to appear in the CISA Known Exploited Vulnerabilities Catalog. However, vigilance is essential as the threat landscape evolves.
In conclusion, the NGINX2Root vulnerabilities highlight ongoing challenges in web server security, emphasizing the need for timely updates and careful infrastructure configuration to safeguard against potential attacks.
