Conversations
NGINX Discloses Two Critical HTTP/2 Remote Code Execution Vulnerabilities
Wiz Research and several other parties independently discovered two critical, unauthenticated remote code execution vulnerabilities in NGINX, tracked as CVE-2026-123633 and CVE-2026-123007, both with a CVSS 4.0 score of 9.2. Exploitation requires HTTP/2 to be enabled, and attackers could potentially take control of servers, steal data, or disrupt services. F5 released security updates on November 18.
NGINX is commonly used to receive and forward traffic for production applications and APIs. Researchers said the vulnerabilities reside in NGINX itself, meaning even if a website or API's own application code is secure, it can still be exposed through the underlying NGINX deployment. Because one NGINX instance often serves as the traffic entry point for multiple applications, a single affected deployment can affect numerous services.
Both vulnerabilities require HTTP/2 to be enabled on the affected server, along with their own additional conditions. CVE-2026-123007 can be traced back to NGINX version 1.9.5 from 2015, and the related integer underflow issue had remained hidden for more than a decade; the other use-after-free vulnerability has existed for nearly six years. Researchers' tests showed that CVE-2026-123007 can execute code on NGINX serving only ordinary static files, with no backend application or third-party modules.
The disclosure timeline shows that Wiz reported the first vulnerability to F5, the company behind NGINX, on October 21, saying it had confirmed remote code execution combined with an ASLR bypass; F5 said at the time that another team had already reported the same issue. On November 10, F5 provided a patch for review, and on November 16 Wiz reported the second HTTP/2 vulnerability. The next day, F5 confirmed that it corresponded to CVE-2026-123007 and included it in the planned release, followed by the security release and coordinated disclosure on November 18. The researchers recommend that organizations inspect affected deployments and upgrade to the latest version containing multiple security fixes.