NGINX fixes critical HTTP/2 code execution flaw dating to 2015

F5 has released fixes for five critical NGINX vulnerabilities, including CVE-2026-123007, a decade-old HTTP/2 flaw that can allow an unauthenticated attacker to execute code on a server with HTTP/2 enabled. The issue, dubbed “nginx2root”, has existed in the NGINX open-source codebase since version 1.9.5, released in September 2015.
NGINX Open Source versions 1.31.9 and 1.30.7 fix all five flaws. F5 rates each vulnerability at 9.2 out of 10 under CVSS 4.0. The vendor said the code-execution condition applies where address space layout randomization (ASLR) is disabled or can be bypassed; Wiz reported bypassing ASLR and achieving code execution in its tests.
HTTP/2 exposure is central to the primary flaw
CVE-2026-123007 requires HTTP/2 to be enabled. Researchers at Xint said their test exploit needed only a reachable HTTP/2 port, and code executed through the vulnerability inherits the permissions of an NGINX worker process. CIRCL, the Computer Incident Response Center Luxembourg, noted that obtaining root privileges on the host requires a separate privilege-escalation path.
In Xint’s testing, worker-level execution was combined with a separate Linux kernel SCTP vulnerability to reach root, including when NGINX ran inside a Docker container. F5, Wiz and Rapid7 had not reported observed exploitation at the time of publication, and CISA had not added the issue to its Known Exploited Vulnerabilities catalog. Public proof-of-concept code is available, although its notes describe a demonstration against a freshly started local Docker container.
Affected versions and additional attack paths
All open-source releases from 1.9.5 through 1.31.8 are vulnerable to CVE-2026-123007. NGINX Plus is also affected in 37.x releases before the fixed builds and in R34 through R36. For NGINX Plus, versions 37.3.0.1 and 37.0.8.1 fix four of the five issues; the fix for CVE-2026-123633 was introduced earlier in 37.2.0.1 and 37.0.7.1. No fix was listed for R34 to R36.
The other vulnerabilities have distinct prerequisites. CVE-2026-123633 involves HTTP/2, proxying to a backend and pressure on worker_connections. CVE-2026-123634 needs a proxied server name built from variables and an SSI or mirror subrequest. CVE-2026-121810 requires HTTP/3, while CVE-2026-113425 affects NGINX used as a mail proxy.
Upgrade, restart and validate exposure
After applying an update, administrators must fully restart NGINX or use its live binary upgrade. A configuration reload alone leaves the old executable running, and existing connections may remain assigned to old worker processes. The official NGINX Docker images had tags for 1.31.9 and 1.30.7, including Alpine variants, while Ubuntu and Debian had not yet shipped fixed packages at publication time.
Where an immediate update is not possible, CIRCL recommends disabling HTTP/2 as a temporary mitigation for CVE-2026-123007 and CVE-2026-123633. On NGINX 1.25.1 and later, this requires setting http2 off; in affected server blocks and removing HTTP/2 from listen directives. Older versions require removing http2 from each listen directive. HTTP/3 should also be disabled where it is not required to remove the condition for CVE-2026-121810.
Teams should check the origin server rather than relying on a CDN-facing endpoint, because an origin that accepts only HTTP/1.1 cannot be reached through HTTP/2. They should also investigate unexpected programs started by NGINX workers, abnormal worker exits or core dumps, long-lived HTTP/2 connections with substantial incoming traffic but few logged requests, and unusual outbound connections or DNS lookups. A clean access log is not conclusive because HTTP/2 control frames do not normally appear as requests. The practical priority is to inventory exposed NGINX instances, deploy the applicable fixed build, perform a full restart and validate that unnecessary HTTP/2, HTTP/3 and mail-proxy services are disabled.

