Decade-Old NGINX HTTP/2 Flaw Enables Unauthenticated Code Execution
Nginx
A decade-old vulnerability inside NGINX's HTTP/2 implementation has become one of the biggest web infrastructure emergencies of the year. Disclosed on November 18, 2026 alongside out-of-band patches from F5, the flaw, tracked as CVE-2026-123007, dubbed "nginx2root," and rated 9.2 on CVSS 4.0, allows unauthenticated attackers to execute code on servers with HTTP/2 enabled. The bug has existed in NGINX open source since version 1.9.5 was released on September 22, 2015, and fixed releases 1.31.9 and 1.30.7 shipped on November 18.
Neither F5 nor researchers at Wiz and Rapid7 have reported active exploitation in the wild yet, and CISA's Known Exploited Vulnerabilities catalog did not list it as of November 18. Even so, proof-of-concept exploit code is already on GitHub—though its notes state it is only suited for demonstrating the attack against a freshly started Docker container on the same machine—and researchers have shown working remote code execution (RCE) in tests. F5 says code execution is possible where Address Space Layout Randomization (ASLR) is off or bypassed; Wiz bypassed ASLR and ran code on official NGINX 1.31.7 and 1.31.8 builds over HTTP/2 with TLS on 64-bit systems, while Xint achieved RCE over a reachable HTTP/2 port against test servers on AWS, GCP, and Azure, including over a public IP address.
How CVE-2026-123007 Corrupts Memory
At the code level, CVE-2026-123007 is an integer underflow (CWE-191) inside ngx_http_v2_module, which tracks flow-control credit for outbound HTTP/2 data. Clients grant window credits so the server does not flood the receiver, and NGINX tracks those credits across individual streams as well as the shared connection.
According to researcher breakdowns, an attacker can corrupt memory over an HTTP/2 session through a sequence of stream and credit manipulations:
- Queuing and Stream Cancellation: A remote, unauthenticated client slows its reading of server output so outbound
DATAframes stay queued while connection credits climb toward maximum bounds and stream credits sit just below that ceiling. Sending aSETTINGSframe that raisesSETTINGS_INITIAL_WINDOW_SIZEpast the stream limit closes streams while keeping the connection alive, and cleaning up those closed streams can restore reserved credit past maximum limits. - Connection Credit Underflow: Follow-up
WINDOW_UPDATEframes and subtraction checks on connection-level counters underflow (CWE-191), pushing the unsigned 64-bit counter into a massive range. - Signed vs. Unsigned Length Mismatch: When NGINX's output filter converts that oversized unsigned counter into a signed 64-bit length (
off_t) or buffer calculation, it can produce a negative response length and an invalid buffer state. - Out-of-Bounds
memcpyand Code Execution: Buffered TLS output routines can pass a huge unsigned byte count intomemcpy, triggering out-of-bounds memory reads and writes. Rapid7 noted its exploit against a 64-bit Linux container running NGINX 1.31.8 with HTTP/2 and TLS required about 128 GB of HTTP/2 traffic over one connection—taking two and a half minutes in its demo, whereas links slower than roughly 300 Mbit/s would run past NGINX's default one-hour connection limit and fail—and relied on aglibcmemory-copy routine selected on x86-64 CPUs withavx512fandavx512vlfeatures. Researchers have shown that leaking memory addresses to resolve functions past ASLR and hijacking a cleanup callback allows code execution in the NGINX worker process.
Five Critical Flaws and the Path to Host Root
Code run via CVE-2026-123007 lands with NGINX worker privileges, not host root. According to the Computer Incident Response Center Luxembourg (CIRCL), reaching host root requires a second privilege-escalation step. In Xint's tests, code running as a worker reached host root, even inside a Docker container, by chaining with a separate bug in the Linux kernel's Stream Control Transmission Protocol (SCTP) code.
F5's November 18 release addresses ten vulnerabilities in total, including four other critical flaws rated 9.2 on CVSS 4.0 that can lead to code execution under the same ASLR condition when specific setups are present:
CVE-2026-123007: Requires HTTP/2 turned on (via alistendirective withhttp2orhttp2 on;).CVE-2026-123633: Requires HTTP/2 enabled with requests passed to a backend server while a worker is running low onworker_connections.CVE-2026-123634: Requires a proxied server name built from variables plus a Server-Side Include (SSI) ormirrorsubrequest to a location looking up that same name.CVE-2026-121810: Requires HTTP/3 turned on.CVE-2026-113425: Requires NGINX used as a mail proxy.
What This Means for Canadian Infrastructure
Across Canada, NGINX sits in front of public websites, reverse proxies, API gateways, and cloud workloads across banking, telecom, healthcare, retail, and government. Even when an upstream app server is locked down, compromising an NGINX worker exposes in-memory TLS traffic, session tokens, secrets, and internal network paths.
The Canadian Centre for Cyber Security (CCCS) published advisory AV26-1174 on November 18, 2026, flagging F5's NGINX advisories for Canadian defenders. Critical infrastructure and regulated operators should treat patching and hardening as a priority in line with Bill C-26 expectations and Communications Security Establishment (CSE) / CCCS guidance, while teams subject to PIPEDA or Quebec's Law 25 should factor edge-proxy compromise into incident response and breach assessments with the Office of the Privacy Commissioner of Canada (OPC) or provincial regulators where applicable.
What Defenders Should Do Now
- Check Exposure and Package Status: Test internet-facing NGINX servers, and test NGINX origins directly behind CDNs, since an origin accepting only HTTP/1.1 cannot be hit over HTTP/2, using
openssl s_client -connect <host>:443 -alpn h2(looking forALPN protocol: h2). Official Docker images had1.31.9and1.30.7tags (including Alpine variants) on November 18, whereas Ubuntu (16.04 through 26.10) and Debian (bookworm,trixie,forky, andsid) had not shipped fixed packages as of that date; because distros can backport fixes without changingnginx -voutput, compare full package versions against your distribution's advisory. - Upgrade and Restart Fully: Per F5, NGINX Open Source
1.31.0through1.31.8(mainline) is fixed in1.31.9, and1.9.5through1.30.6(including older branches like1.28) is fixed in1.30.7, with both fixing all five flaws. On NGINX Plus,37.1.0through37.2.0.1is fixed in37.3.0.1and37.0.0through37.0.7.1is fixed in37.0.8.1(withR34throughR36having no fix listed;37.3.0.1and37.0.8.1fix four of the five flaws, whileCVE-2026-123633was fixed in earlier builds37.2.0.1and37.0.7.1). Perform a full restart or live binary upgrade after updating—a reload alone leaves the old binary running and existing connections on old workers. - Apply Workarounds and Block SCTP: CIRCL notes disabling HTTP/2 temporarily blocks
CVE-2026-123007andCVE-2026-123633(on 1.25.1+, sethttp2 off;in affected server blocks and removehttp2fromlistendirectives; on 1.9.5 through 1.25.0, removehttp2fromlistendirectives such aslisten 443 ssl http2;tolisten 443 ssl;), then restart where needed and re-check withopenssl s_client. Disabling HTTP/3 addressesCVE-2026-121810, while F5 lists workarounds forCVE-2026-123634(avoid SSI andmirrordirectives and do not build proxied server names from variables) andCVE-2026-113425(restrict mail proxy listeners to trusted networks). For the Linux SCTP flaw, CIRCL advises blocking module loading on hosts not using SCTP viainstall sctp /bin/falsein/etc/modprobe.d/(which does not unload an already-loaded module or disable built-in kernel SCTP). - Watch for Signs of Attack: CIRCL recommends checking for NGINX workers launching unexpected programs, workers crashing abnormally or dropping core dumps, long-lived HTTP/2 connections with heavy inbound traffic and few logged requests, and unusual outbound connections or DNS lookups—noting that clean access logs do not rule out an attack since HTTP/2 control frames typically do not appear as requests there, and no single indicator is proof on its own.
The vulnerabilities in this story
-
Not yet rated by the NVD: see the record on cve.org.
-
Not yet rated by the NVD: see the record on cve.org.
-
Not yet rated by the NVD: see the record on cve.org.
-
Not yet rated by the NVD: see the record on cve.org.
-
Not yet rated by the NVD: see the record on cve.org.
Scores and dates: NVD (not endorsed by the NVD). Each ID opens its record on cve.org.

