NEWS

nginx2root: 10-Year-Old NGINX HTTP/2 Flaw CVE-2026-123007 Allows Unauthenticated Code Execution

CVE-2026-123007 (CVSS 9.2) affects NGINX 1.9.5 through 1.31.8 with HTTP/2 enabled. Upgrade to 1.31.9 or 1.30.7 and fully restart. No exploitation reported yet.

Dylan H.

News Desk

November 18, 2026
3 min read
nginx2root: 10-Year-Old NGINX HTTP/2 Flaw CVE-2026-123007 Allows Unauthenticated Code Execution

Summary

A decade-old flaw in NGINX's HTTP/2 support, CVE-2026-123007 and nicknamed "nginx2root", can let an unauthenticated remote attacker run code on servers with HTTP/2 enabled. It scores CVSS 4.0 9.2 and has been present in open-source NGINX since version 1.9.5, released September 22, 2015. It is an integer underflow.

Fixes shipped today alongside four other flaws that also score 9.2.

Affected and fixed versions

ProductAffectedFixed in
NGINX OSS mainline1.31.0 – 1.31.81.31.9
NGINX OSS stable and older1.9.5 – 1.30.61.30.7
NGINX Plus37.1.0 – 37.2.0.137.3.0.1
NGINX Plus37.0.0 – 37.0.7.137.0.8.1
NGINX PlusR34 – R36No fix listed

What an attacker needs

  • HTTP/2 enabled on a listener (http2 in listen, or http2 on).
  • ASLR disabled or bypassed. F5 says code runs only in that case, though Wiz bypassed ASLR in tests and Xint ran code with just a reachable HTTP/2 port.
  • Code runs with NGINX worker privileges. Xint says reaching root needs a second bug, a Linux kernel SCTP flaw that is not yet fixed.
  • Rapid7's analysis needs about 128 GB of HTTP/2 traffic (around 2.5 minutes in the demo) and relies on a glibc memory-copy routine used on x86-64 CPUs with avx512f and avx512vl. Slow links would hit NGINX's default one-hour connection limit.

Exploitation status

No in-the-wild attacks have been reported, and the flaw is not in CISA KEV. A public proof-of-concept exists on GitHub, but its notes say it only suits a freshly started Docker container on the same machine.

Four other flaws fixed

CVERequired setup
CVE-2026-123633HTTP/2, with requests passed to a backend while the worker is low on worker_connections
CVE-2026-123634Proxied server name built from variables, plus SSI or a mirror subrequest
CVE-2026-121810HTTP/3 enabled
CVE-2026-113425NGINX used as a mail proxy
  1. Upgrade to 1.31.9, 1.30.7 or the fixed Plus build, then do a full restart or live binary upgrade. A reload alone keeps the old executable running.
  2. Temporary workaround: disabling HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633 but not the other three. On 1.25.1 and later set http2 off; per server block. On 1.9.5 through 1.25.0 remove http2 from listen.
  3. Disable HTTP/3 where unneeded, avoid SSI and mirror with variable-built server names, and limit mail proxy listeners to trusted networks.
  4. On hosts that do not use SCTP, block the module with install sctp /bin/false in a file under /etc/modprobe.d/.
  5. Distribution packages: Ubuntu and Debian had not shipped fixes at the time of reporting. Compare full package versions against distro advisories, since backports may not change nginx -v.
  6. Hunt for workers spawning unexpected programs, abnormal worker exits or core dumps, long-lived HTTP/2 connections with heavy inbound traffic but few logged requests, and unusual outbound connections.

Source