November 19, 2026 / news

Decade-Old NGINX HTTP/2 Flaw (CVE-2026-123007) Enables Unauthenticated RCE, Fixed in 1.31.9 and 1.30.7

NGINX 1.31.9/1.30.7 fix CVE-2026-123007, an HTTP/2 flow-control memory corruption present since 1.9.5 (2015) that researchers demonstrated into unauthenticated code execution; HTTP/2 off is the stopgap.

Title: NGINX 1.31.9 and 1.30.7 Close a Ten-Year-Old HTTP/2 Bug That Researchers Turned Into Unauthenticated Code Execution

Summary: F5 shipped NGINX 1.31.9 and 1.30.7 on November 18, 2026, fixing CVE-2026-123007, a memory corruption in HTTP/2 flow control that NGINX’s own security advisories rate “major” and list as affecting every open-source release from 1.9.5 (September 2015) through 1.31.8 — roughly a decade of defaults, including 1.30.6 and 1.31.8 from October. No credentials are involved — a reachable HTTP/2 listener is enough. Wiz’s team got code running by defeating ASLR; Xint’s attack landed on test servers across AWS, GCP and Azure, including from a public IP; and Rapid7’s slower variant burns roughly 128 GB of HTTP/2 traffic (about two and a half minutes in its demo) and rides on a glibc memory-copy routine selected on x86-64 CPUs carrying the AVX-512 feature set. Whatever runs this way keeps only an NGINX worker’s privileges; reaching root demands a second privilege-escalation bug, and CIRCL points out that in Xint’s testing an unrelated SCTP flaw in the Linux kernel supplied exactly that — even with NGINX boxed inside a Docker container. A PoC exists on GitHub, though its own documentation scopes it to attacking a freshly started Docker container on the same host; neither F5 nor the Wiz and Rapid7 researchers have observed real attacks, and the bug was absent from CISA’s KEV catalog when the disclosure landed. Alongside CVE-2026-123007, the batch closes four further memory-safety bugs (CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425) that F5 also scores 9.2 and warns can end in code execution when ASLR is missing or beaten — yet each needs its own narrow setup: HTTP/2 proxying while the worker runs short of worker_connections; a proxied server name assembled from variables combined with SSI or mirror subrequests; HTTP/3; or the mail proxy role. The fix for CVE-2026-123007 exists only in 1.31.9 and 1.30.7 (NGINX Plus 37.3.0.1 and 37.0.8.1, with R34–R36 still unfixed); Ubuntu and Debian had not shipped fixed packages at disclosure. Until a patch is possible, CIRCL’s stopgap is to disable HTTP/2 — from 1.25.1 onward via http2 off; in each affected server block plus dropping http2 from its listen directives, on older builds by editing listen 443 ssl http2; down to a plain ssl listener — and, where SCTP is not actually used, to stop the kernel module loading with an install sctp /bin/false line under /etc/modprobe.d/. Once the new build is in, a full restart or a live binary upgrade is needed; a bare reload can keep the previous executable and its worker processes serving existing connections. Confirm the change with openssl s_client -alpn h2. Hunting for past attempts is difficult: CIRCL points to workers launching programs they have no business starting, abnormal terminations or core dumps left behind, HTTP/2 sessions that stay open for a long time while pulling large volumes of data but generating only a handful of log entries, and outbound traffic or DNS lookups that do not belong. An empty access log is no comfort — HTTP/2 control frames leave no request entries — and none of these signals is conclusive alone.

References:

← All news