Security
NGINX2Root (CVE-2026-123007): Five Critical NGINX Flaws Expose HTTP/2 Servers to Worker RCE
Disclosed on November 18, 2026, NGINX2Root bundles five unauthenticated NGINX vulnerabilities—led by CVE-2026-123007 (CVSS 4.0: 9.2)—that can grant worker-level remote code execution and chain with a Linux kernel SCTP bug for host root. Learn which NGINX Open Source and NGINX Plus builds are affected, why ASLR alone won't save you, and how to disable HTTP/2 until you upgrade to 1.30.7 or 1.31.9.
9 min read
NGINX2Root (CVE-2026-123007): Five Critical NGINX Flaws Expose HTTP/2 Servers to Worker RCE
Executive Summary
On November 18, 2026, F5 and the NGINX project disclosed NGINX2Root, a cluster of five unauthenticated remote code execution (RCE) vulnerabilities in NGINX Open Source and NGINX Plus—led by CVE-2026-123007 (also referred to as NGINX2Shell), an HTTP/2 flow-control integer overflow present in upstream NGINX since version 1.9.5 (September 2015). F5 rates the vulnerabilities CVSS v4.0 9.2 (Critical) and CVSS v3.1 8.1 (High).
Discovered and published by Theori's Xint research team (with independent discoveries of CVE-2026-123007 and CVE-2026-123633 credited to Rapid7, Wiz, Ikotas Labs, Palo Alto Networks, and Metnir), the five flaws allow unauthenticated remote attackers to crash NGINX worker processes, corrupt heap memory, bypass Address Space Layout Randomization (ASLR), and execute arbitrary commands with NGINX worker privileges. Xint also demonstrated chaining worker-level RCE with a separate, unpatched Linux kernel SCTP use-after-free vulnerability (present since Linux 4.15) to escalate to host root, including from inside a Docker container.
Fixed upstream builds—NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), plus NGINX Plus PLS.37.0.8.1 (LTS) and PLS.37.3.0.1 (CR)—shipped on November 18, 2026. Although no wild exploitation has been reported and none of the five CVEs appeared in CISA's Known Exploited Vulnerabilities (KEV) catalog as of November 18–19, 2026, Rapid7 published a working proof-of-concept (PoC) exploit for CVE-2026-123007 on GitHub. Teams running internet-facing NGINX instances with HTTP/2 enabled should upgrade and restart (not merely reload) NGINX immediately, or disable HTTP/2 as a temporary containment measure.
| CVE ID | Component / Protocol | Affected Scope | Temporary Mitigation |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow control (WINDOW_UPDATE overflow) |
NGINX 1.9.5 – 1.31.8 with HTTP/2 enabled |
Disable HTTP/2 (http2 off;) |
| CVE-2026-123633 | HTTP/2 upstream proxying (use-after-free on low connections) | NGINX 1.19.7 – 1.31.8 with HTTP/2 + upstream proxy |
Disable HTTP/2 (http2 off;) |
| CVE-2026-123634 | DNS resolver + variable proxy_pass + mirror/SSI |
0.6.18+ (F5) / 1.13.4+ (Xint tested) |
Fixed upstream group; disable mirror |
| CVE-2026-121810 | HTTP/3 (QUIC) connection close during active request | NGINX 1.25.0+ with HTTP/3 enabled |
Remove QUIC listeners; http3 off; |
| CVE-2026-113425 | Mail proxy (proxy on + auth_http) |
0.5.33+ (F5) / 0.5.15+ (Xint tested) |
Bind mail proxy to loopback / firewall |
Technical Mechanics and Architecture
How CVE-2026-123007 Corrupts Memory and Bypasses ASLR
In HTTP/2, clients use WINDOW_UPDATE frames to advertise how much response data the server is allowed to send. In CVE-2026-123007, NGINX subtracts queued response bytes from the connection's send window and restores that credit if a stream is canceled before transmission completes.
When a client inflates the connection send window using WINDOW_UPDATE frames while response data sits in the queue and then cancels the stream at the right moment, NGINX's cleanup path adds the credit back a second time without enforcing the HTTP/2 protocol maximum. The send window exceeds its upper bound, causing a capacity check to underflow and subsequent updates to wrap into an enormous signed-to-unsigned copy length. That out-of-bounds heap copy corrupts adjacent heap metadata and leaks memory addresses—enabling attackers to bypass ASLR and PIE (Position-Independent Executable) protections and hijack control flow via an overwritten cleanup callback.
The Four Companion Use-After-Free Flaws & Kernel Root Chain
- CVE-2026-123633 (HTTP/2 Upstream Proxy UAF): Triggered when HTTP/2 is enabled, requests are proxied to an upstream backend, and worker connections approach exhaustion, causing connection-draining logic to free a request structure that is still in flight.
- CVE-2026-123634 (DNS Resolver UAF): Triggered via a crafted HTTP request when NGINX uses a dynamic
resolver, a variable-basedproxy_pass, andmirror(withmirror_request_body off) or SSI subrequests resolving the same name. - CVE-2026-121810 (HTTP/3 QUIC UAF): Triggered when a QUIC connection closes while an HTTP/3 request is still executing.
- CVE-2026-113425 (Mail Proxy UAF): Triggered in the NGINX mail proxy's
auth_httpauthentication path. - Unpatched Linux Kernel SCTP Flaw: Xint chained worker-level RCE from
CVE-2026-123007with a separate use-after-free/double-free in the Linux kernel's SCTP send path (present since Linux4.15, with no CVE or kernel patch published at disclosure) to escape containers and gain host root.
Attack Surface & Privilege-Escalation Architecture
+-------------------------------------------------------------------------+
| UNAUTHENTICATED REMOTE ATTACKER |
| - Sends long-lived HTTP/2 connection with WINDOW_UPDATE + stream |
| cancellations (CVE-2026-123007) -> ~119 GiB plaintext in Rapid7 PoC |
+------------------------------------+------------------------------------+
|
v
+-------------------------------------------------------------------------+
| NGINX WORKER PROCESS (1.9.5 - 1.31.8, HTTP/2 Enabled) |
| 1. Heap memory leak -> bypasses ASLR / PIE |
| 2. Overwrites cleanup callback -> RCE as NGINX worker UID |
| 3. Exposes decrypted TLS traffic, session tokens, & software TLS keys |
+------------------------------------+------------------------------------+
|
+-------------------------+-------------------------+
| |
v v
+-------------------------+ +---------------------+
| BACKEND / UPSTREAM PIVOT| | LINUX KERNEL 4.15+ |
| - Trusted internal APIs | | SCTP Send-Path UAF |
| - East-west lateral hop | | -> HOST ROOT (even |
+-------------------------+ | from Docker) |
+---------------------+
Defensive Verification & Containment Snippets
1. Safe Host Exposure Audit Script (Read-Only):
#!/usr/bin/env bash
# Read-only NGINX2Root exposure audit (version, HTTP/2 module, config, and OS package)
set -euo pipefail
echo "=== NGINX Binary & Modules ==="
nginx -v 2>&1 || true
nginx -V 2>&1 | tr ' ' '\n' | grep -E 'http_v2_module|http_v3_module|mail' || true
echo "=== Active HTTP/2 & HTTP/3 Directives ==="
sudo nginx -T 2>/dev/null | grep -nE 'http2|http3|quic|resolver|mirror|auth_http' || echo "None found"
echo "=== Distro Package Version (Check Backports on Debian/Ubuntu/RHEL) ==="
if command -v dpkg-query >/dev/null 2>&1; then
dpkg-query -W -f='${Package} ${Version}\n' 'nginx*' 2>/dev/null || true
elif command -v rpm >/dev/null 2>&1; then
rpm -qa 'nginx*' 2>/dev/null || true
fi
2. Temporary HTTP/2 Containment & Kernel SCTP Hardening:
# Temporary mitigation for CVE-2026-123007 and CVE-2026-123633 (NGINX 1.25.1+)
# Place in http {} or server {} block until upgraded to 1.30.7 / 1.31.9.
# Note: Native gRPC services requiring HTTP/2 will stop working.
http2 off;
# Prevent automatic loading of the Linux SCTP kernel module if unused
# Note: Does not unload an already-loaded module or disable built-in SCTP.
echo "install sctp /bin/false" | sudo tee /etc/modprobe.d/disable-sctp.conf
Evidence & Operational Impact
PoC Availability, Constraints, and Cloud Validation
- Xint & Rapid7 Demonstrations: Xint demonstrated CVE-2026-123007 against public HTTPS IP addresses across AWS, GCP, and Azure. On November 19, 2026, CIRCL (TR-105) confirmed that Rapid7 published a public PoC on GitHub targeting NGINX 1.31.8 on Linux/amd64 Docker images.
- Practical Exploitation Constraints: CIRCL and Qualys note that Rapid7's public PoC is bandwidth- and environment-sensitive—it requires approximately 119 GiB (128 GB) of transmitted plaintext over a single long-lived HTTP/2 connection, relies on a specific
glibcmemory-copy routine and CPU features, and sees reduced reliability on busy workers with concurrent clients. While these constraints slow mass automated exploitation, researchers emphasize that they do not protect exposed servers against determined attackers. - CDNs, WAFs, and F5 BIG-IP: CDNs or WAFs that terminate HTTP/2 before forwarding to NGINX may strip or normalize the malformed
WINDOW_UPDATEsequence, depending on implementation. Separately, F5 clarified on November 19, 2026 that F5 BIG-IP (all modules) is not vulnerable toCVE-2026-123007orCVE-2026-123633, though NGINX reverse proxies sitting behind BIG-IP remain in scope if they receive HTTP/2 directly.
Source Discrepancies & Missing Benchmarks
- Version Scope Differences: F5 and
nginx.orgtraceCVE-2026-123634back to0.6.18andCVE-2026-113425back to0.5.33, whereas Xint listed1.13.4and0.5.15for the specific paths it tested. - Distro Package Lag: As of November 18, 2026, Alpine Linux 3.24 (
1.30.7-r0), Arch Linux (1.30.7-1/1.31.9-1), and official Docker images (1.30.7/1.31.9) shipped patched builds, whereas Debian and Ubuntu had not yet released fixed packages. - Performance Benchmarks: Quantitative throughput or latency benchmarks comparing
1.30.7/1.31.9against prior releases (or measuring fallback to HTTP/1.1) are unavailable in the fetched advisories.
Hardening Playbook
Audit Exact Package & Container Versions
- Do not rely solely on
nginx -vor externalServer:banners, because Linux distributions backport patches without changing upstream version strings. Checkdpkg-queryorrpm -qaagainst your OS vendor's advisory, and inventory every container image (FROM nginx:...) and embedded NGINX runtime.
- Do not rely solely on
Patch to Fixed Releases and Restart (Do Not Just Reload)
- Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), and NGINX Plus to PLS.37.0.8.1 (LTS) or PLS.37.3.0.1 (CR) (note:
CVE-2026-123633was also addressed inPLS.37.0.7.1/PLS.37.2.0.1). - Critical Operational Step: Run a full restart (
systemctl restart nginx) or live binary upgrade after patching. A simplenginx -s reloadupdates configuration only and leaves the vulnerable binary running in existing worker processes.
- Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), and NGINX Plus to PLS.37.0.8.1 (LTS) or PLS.37.3.0.1 (CR) (note:
Apply Interim Protocol & Feature Mitigations Where Patching Waits
- HTTP/2 (
CVE-2026-123007,CVE-2026-123633): Sethttp2 off;(NGINX 1.25.1+) or removehttp2fromlistendirectives (older releases) and test gRPC dependencies first. - Resolver/Mirror (
CVE-2026-123634): Replace request-derivedproxy_passwith fixedupstreamblocks and disable unusedmirror/SSI features. - HTTP/3 (
CVE-2026-121810) & Mail (CVE-2026-113425): Removequiclisteners / sethttp3 off;, and bind mail proxies to127.0.0.1or restrict via firewall.
- HTTP/2 (
Monitor for Long-Lived HTTP/2 Anomalies & Worker Compromise
- Because HTTP/2 control frames are encrypted and absent from standard access logs, monitor
ss -tinpfor long-lived connections with rapidly growingbytes_receivedand minimalbytes_sent, inspecterror.logandcoredumpctl list nginxfor worker crashes, and enforceauditdrules alerting onexecvesyscalls spawned by thenginx/www-dataworker UID:
# Auditd rule to detect shell/binary execution by NGINX worker UID (replace 33 with actual UID) sudo auditctl -a always,exit -F arch=b64 -S execve -F uid=33 -k nginx_worker_exec- Because HTTP/2 control frames are encrypted and absent from standard access logs, monitor
Rollback & Change-Control Notes
- If disabling HTTP/2 breaks gRPC or HTTP/2-dependent frontends, restore
http2 on;only behind a verified HTTP/2-terminating WAF/CDN while prioritizing an emergency container/package rebuild to1.30.7/1.31.9. - Before adding
install sctp /bin/false, confirm no clustering, telecom, or specialized transport workloads on the host depend on SCTP.
- If disabling HTTP/2 breaks gRPC or HTTP/2-dependent frontends, restore
Frequently Asked Questions (FAQ)
1. Does ASLR or compiling NGINX with PIE stop CVE-2026-123007? No. Both CIRCL (TR-105) and Rapid7's public PoC confirm that attackers can leak memory addresses via the heap overflow to bypass ASLR and PIE before hijacking execution.
2. Is nginx -s reload enough after installing the security update?
No. Reloading only re-reads configuration files and spawns new workers from the old binary in memory if not upgraded properly, or leaves old connections in old workers. Always perform a full service restart or live binary upgrade, and rebuild/redeploy container images.
3. Are NGINX servers behind Cloudflare or another CDN still vulnerable?
If the CDN or WAF terminates HTTP/2 at the edge and communicates with your NGINX origin over HTTP/1.1, the HTTP/2 attack paths (CVE-2026-123007 and CVE-2026-123633) are mitigated at the edge. However, if attackers can reach your origin IP directly—or if your origin uses the vulnerable resolver, HTTP/3, or mail proxy features—you remain exposed.
4. Is F5 BIG-IP affected by NGINX2Root?
According to F5's November 19, 2026 clarification, all F5 BIG-IP modules are not vulnerable to CVE-2026-123007 or CVE-2026-123633. However, any NGINX Open Source or NGINX Plus instance deployed behind BIG-IP must still be patched.
5. Is there a patch for the Linux kernel SCTP bug used in the root chain?
As of November 19, 2026, no CVE ID or official Linux kernel patch has been published for the SCTP send-path use-after-free. Xint has withheld the final kernel escalation steps, and CIRCL recommends blacklisting the sctp module via /etc/modprobe.d/ on hosts that do not require it.
Sources
- CIRCL Technical Report (TR-105) — NGINX2ROOT – Remote Code Execution in NGINX via HTTP/2 and Other Attack Surfaces. Published: November 18, 2026 (Updated Version 1.1: November 19, 2026). URL: https://www.circl.lu/pub/tr-105/
- CERT-EU Security Advisory (2026-022) — Critical vulnerabilities in Nginx (referencing F5 K000164058 and Xint). Published: November 19, 2026. URL: https://www.cert.europa.eu/publications/security-advisories/2026-022/
- Qualys Blog — NGINX2Root: Five nginx Flaws, Led by CVE-2026-123007. How to Find, Mitigate, and Patch Now. Published: November 19, 2026. URL: https://blog.qualys.com/product-tech/patch-management/2026/11/18/nginx2root-five-nginx-flaws-led-by-cve-2026-123007-how-to-find-mitigate-and-patch-now
- Help Net Security — NGINX2Root: F5 patches five critical NGINX vulnerabilities. Published: November 20, 2026. URL: https://www.helpnetsecurity.com/2026/11/19/nginx2root-nginx-vulnerabilities/
- Cloudflare Radar (Zero Wire) — nginx2root: remote code execution in nginx HTTP/2 and four companion flaws. Published: November 18, 2026. URL: https://radar.cloudflare.com/zero-wire/nginx2root