Millions of NGINX Servers Remain Vulnerable to ‘NGINX2Root’ Exploit

Roughly 8.8 million NGINX services are still open to a newly disclosed set of critical memory vulnerabilities dubbed “NGINX2Root.” The flaws were made public by security firm Xint on November 18, 2026, spotlighting a series of risks that could allow remote attackers to execute commands as NGINX worker processes. Around 441,000 additional services once exposed are now patched or have dropped HTTP/2 support.

What’s at Stake & Which Servers Are Affected

NGINX2Root encompasses five distinct memory-based bugs in NGINX. The most dangerous among them—CVE-2026-123007—has been present in all official NGINX releases from version 1.9.5 through 1.31.8, dating back to 2015 when HTTP/2 support was introduced. That bug alone requires only HTTP/2 to be enabled. Other vulnerabilities in the set need additional features like backend proxies, HTTP/3 usage, runtime DNS lookups, or mail proxy configurations with certain authentication modules. Each of the flaws exceeds a CVSS v3.1 score of 8.0 and scores about 9.2 under CVSS v4.0.

Disabling HTTP/2 mitigates only two of the five issues; servers operating with HTTP/3, mail proxy setups, or runtime DNS configurations remain vulnerable until patched. Current tracking by Censys estimates over 331 million NGINX web properties exist, with roughly a third hiding their version numbers—making exposure assessments difficult. Of those services visible and running HTTP/2, 8,823,450 match the vulnerable version range.

Detection, Exploitation Status & Technical Details

Security teams have developed lightweight tests for CVE-2026-123007 that are far less resource intensive than earlier proof-of-concepts. These tests confirm vulnerability by sending small HTTP/2 payloads—only around 5.69 MB—in contrast to earlier exploits requiring tens of gigabytes. Meanwhile, attempts to reproduce attacks for several other vulnerabilities succeeded, especially those tied to the mail proxy and runtime DNS features, though at least one of the five hasn’t yet been shown to allow code execution.

Even though the bugs are new, there’s no confirmed evidence of exploitation in the wild as of November 18, 2026. The vulnerabilities are not yet listed in the U.S. Critical Infrastructure’s Known Exploited Vulnerabilities catalog. However, the risk remains high given how widespread the vulnerable versions are and how older HTTP/2 implementations have repeatedly surfaced serious flaws over time.

How to Protect Systems Now

Administrators should upgrade immediately to affected-safe versions: NGINX Open Source stable branch to 1.30.7 or later, or mainline to 1.31.9 or newer. If using NGINX Plus, version 37.0.8.1 or 37.3.0.1 marks patched releases. A full service restart—not just a config reload—is required to replace vulnerable binaries.

Where updates aren’t yet possible, organizations should disable HTTP/2 or HTTP/3, limit or secure mail and proxy setups, and avoid using runtime DNS lookups at request time. Monitoring for suspicious behavior—such as frequent worker crashes, long idle connections, and discrepancies in logged request sizes—can help catch early signs of compromise. Access logs will generally not show the hidden protocol frames these bugs exploit.

As protocol features like HTTP/2 and HTTP/3 continue to evolve, so do the opportunities for attack. For NGINX, a foundation of modern web infrastructure, these vulnerabilities highlight both the growing complexity of HTTP and the importance of rapid patching.