Critical Advisory: CVE-2026-123007 (CVSS 9.2) - NGINX2Root

CVE-2026-123007 10-Year-Old NGINX HTTP/2 RCE Scanner

Critical Disclosure: Security researchers uncovered a decade-old vulnerability in NGINX's HTTP/2 protocol module (ngx_http_v2_module) affecting versions 1.9.5 through 1.31.8. Specially crafted flow-control frames trigger an integer underflow leading to heap corruption and remote code execution. Note: standard nginx -s reload does not fix the issue—a full process restart is required.

Continuously audit your internet-facing web applications, reverse proxies, and ingress controllers for CVE-2026-123007 before attackers leverage heap corruption to compromise your web servers and pivot to root access.

  • Full Perimeter NGINX Discovery: Detects every exposed NGINX instance across all ports (80, 443, 8443, 8080) and cloud providers.
  • HTTP/2 & ALPN Protocol Verification: Probes TLS ALPN negotiation (h2) and HTTP/2 directives to distinguish actual attack surfaces from dormant endpoints.
  • Safe, Non-Destructive Probing: Uses banner fingerprinting and protocol handshakes without sending crashing exploit payloads to production workers.
  • Actionable Remediation & Upgrade Verification: Validates package upgrades to 1.30.7+ / 1.31.9+ and verifies that full binary process restarts were executed.
bspeka-scanner // nginx_http2_rce_audit
Critical Severity (CVSS 9.2) gateway.acme-corp.com:443
NGINX HTTP/2 Flow-Control Integer Underflow RCE (CVE-2026-123007)
Detected NGINX 1.27.3 with HTTP/2 (ALPN 'h2') actively negotiated. The ngx_http_v2_module is susceptible to integer underflow in WINDOW_UPDATE stream accounting, leading to heap buffer overflow and remote code execution in worker context.
Upgrade to NGINX 1.31.9+ or 1.30.7+ & run: systemctl restart nginx
Informational gateway.acme-corp.com
TLS ALPN 'h2' Protocol Support Confirmed
SSL handshake negotiated HTTP/2 protocol multiplexing on port 443.
Low Severity gateway.acme-corp.com
NGINX Exact Version Disclosure
Server header leaks 'nginx/1.27.3'. Suppress with 'server_tokens off;'.

Technical Breakdown of CVE-2026-123007 (NGINX2Root)

How a 10-year-old integer underflow in NGINX's HTTP/2 flow-control engine enables heap corruption and remote code execution.

The 10-Year-Old Flow-Control Flaw

Introduced in NGINX 1.9.5 when HTTP/2 support was first implemented in 2015, the ngx_http_v2_module contains an integer calculation error when decrementing stream window sizes during malformed WINDOW_UPDATE and data frame sequences. The integer underflows into an excessively large unsigned value, bypassing boundary checks during buffer allocation.

Heap Corruption to Remote Execution

Because the window size check is circumvented, inbound payload chunks are copied beyond the boundaries of the pre-allocated NGINX pool buffer into adjacent heap memory. Attackers corrupt internal function pointers and request structures, hijacking execution flow under the NGINX worker process user (e.g., nginx or www-data).

The "Reload is Not Restart" Trap

Many system administrators routinely run nginx -s reload or systemctl reload nginx after package manager updates. However, configuration reload only instructs existing master binaries to reload rules. Unless systemctl restart nginx is executed, the old vulnerable binary remains mapped into RAM and exposed to network attacks.

Affected Versions & Remediation Matrix

Identify which NGINX releases require immediate patching and full binary service restart.

Branch / Distribution Vulnerable Versions Patched Version Recommended Action
NGINX Open Source (Mainline) 1.9.5 through 1.31.8 1.31.9+ Upgrade package, run systemctl restart nginx
NGINX Open Source (Stable) 1.10.0 through 1.30.6 1.30.7+ Upgrade package, run systemctl restart nginx
NGINX Plus R9 through R32 R32 P1 / R33 Apply vendor hotfix and full daemon restart
Immediate Mitigation (No Upgrade) Any vulnerable NGINX http2 off; Disable HTTP/2 in server configuration, falls back safely to HTTP/1.1

Frequently Asked Questions

Everything you need to know about CVE-2026-123007 and securing your NGINX deployments.

What is CVE-2026-123007 (NGINX2Root)?
CVE-2026-123007 is a critical CVSS 9.2 vulnerability in NGINX's HTTP/2 implementation (ngx_http_v2_module). Disclosed in November 2026, the vulnerability traces back to the initial introduction of HTTP/2 support in NGINX 1.9.5 ten years ago. It allows unauthenticated remote attackers to trigger heap buffer overflows by manipulating HTTP/2 flow-control window calculations, achieving remote code execution.
Can CVE-2026-123007 lead to root server takeover?
Yes. Initial exploitation yields arbitrary code execution within the NGINX worker process context (typically unprivileged user www-data or nginx). However, security researchers demonstrated that chaining this with local Linux kernel vulnerabilities (such as recent privilege escalation flaws) allows unauthenticated remote attackers to gain unrestricted root access—hence the name "NGINX2Root".
Why isn't a graceful reload (`nginx -s reload`) sufficient?
When you upgrade NGINX via your operating system package manager (e.g. apt upgrade nginx), the binary on disk is updated, but existing master and worker processes in memory continue executing the unpatched code. A graceful reload keeps the master process intact. To load the new, patched binary and flush vulnerable memory structures, you must perform a complete restart: systemctl restart nginx.
What is the temporary workaround if I cannot reboot or upgrade immediately?
You can neutralize the vulnerability by disabling HTTP/2 protocol support:

1. In modern NGINX configurations, add: http2 off; inside the http or server blocks.
2. In older NGINX syntax, remove the http2 token from your listen directive: change listen 443 ssl http2; to listen 443 ssl;.
3. Test configuration: nginx -t
4. Restart daemon: systemctl restart nginx

Client connections will safely negotiate HTTP/1.1 instead.
Does bspeka cause downtime when scanning for this vulnerability?
No. bspeka's scanner performs safe, non-invasive remote protocol interrogation. It validates TLS ALPN protocol handshakes, evaluates NGINX server response characteristics, and checks exact build signatures without sending malicious malformed frame sequences that could crash production worker threads.

Audit Your External Perimeter for CVE-2026-123007

Don't wait for attackers to scan your infrastructure. Discover all vulnerable NGINX servers and exposed HTTP/2 endpoints with bspeka's continuous ASM platform.

Start 14-Day Free Audit