
F5 fixes 10-year-old NGINX HTTP/2 flaw rated 9.2 enabling unauthenticated code execution
F5 fixed CVE-2026-123007, a 10-year-old NGINX HTTP/2 flaw that can let unauthenticated attackers execute code as the worker process. The issue affects open-source versions from 1.9.5 through 1.31.8 and several NGINX Plus releases, with vendor CVSS 9.2. No exploitation was reported as of the release date, but public proof-of-concept code and lagging distribution packages create patching priority.
F5 released NGINX 1.31.9 and 1.30.7 to fix CVE-2026-123007, a flaw in HTTP/2 support present since 1.9.5 in 2015. The flaw, dubbed nginx2root, lets an unauthenticated attacker reach an HTTP/2-enabled listener and run code as the NGINX worker process. F5 says exploitation is possible where ASLR is disabled or bypassed; Wiz said it bypassed ASLR in tests. Xint also said it achieved code execution against a reachable HTTP/2 port.
NGINX advisories rate five related code-execution flaws 9.2 on CVSS 4.0. The affected open-source range runs from 1.9.5 through 1.31.8, including 1.31.7 and 1.30.6. NGINX Plus is affected in 37.x before fixed builds and R34 through R36, though no Plus fix is listed for R34-R36. Public proof-of-concept code exists on GitHub, but its notes limit it to a freshly started Docker container on the same machine. CISA's Known Exploited Vulnerabilities catalog did not list it as of the release date.
The practical exposure depends on deployment. HTTP/2 must be enabled, and a CDN fronting an origin may hide the vulnerable listener; testing the origin with ALPN h2 is the documented check. A separate privilege-escalation step is needed to move from worker to root, but Xint showed a Linux SCTP bug could provide it even inside Docker. Ubuntu and Debian had not shipped fixed packages as of the release date, leaving distribution-managed installs exposed until package updates arrive.
The stakes are operational rather than theoretical: an unauthenticated attacker who reaches an HTTP/2 listener can execute code with worker permissions, and in tested environments a second bug could elevate that to root inside Docker. Distribution packages lagged the vendor release, and a reload alone does not replace the running binary, so patch status must be verified against full package versions.
Organizations running NGINX with HTTP/2 enabled can be exposed to unauthenticated remote code execution at the web worker level, and in tested container setups a second bug could escalate that to root. Patching requires full restarts and verification of distribution or container package versions.
Sources (1)
- [1]Original source(https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html)