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.
h2) and HTTP/2 directives to distinguish actual attack surfaces from dormant endpoints.How a 10-year-old integer underflow in NGINX's HTTP/2 flow-control engine enables heap corruption and remote code execution.
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.
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).
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.
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 |
Everything you need to know about CVE-2026-123007 and securing your NGINX deployments.
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.
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".
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.
http2 off; inside the http or server blocks.http2 token from your listen directive: change listen 443 ssl http2; to listen 443 ssl;.nginx -tsystemctl restart nginxDon'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