
Advisory and technical analysis of CVE-2026-123007, an NGINX HTTP/2 flow-control integer overflow enabling heap corruption and potential RCE, with detection and mitigation steps.
NGINX2ROOT is the research name associated with five memory-corruption vulnerabilities affecting NGINX Open Source and NGINX Plus.
The primary vulnerability, CVE-2026-123007, affects HTTP/2 flow-control handling and can cause a heap-based out-of-bounds write.
Under suitable conditions, an unauthenticated remote attacker can potentially achieve remote code execution with NGINX worker privileges.
β οΈ Remote code execution does not automatically mean root access. Additional privilege escalation would be required to compromise the host as root.
| Attribute | Details |
|---|---|
| Vulnerability | NGINX2ROOT |
| CVE | CVE-2026-123007 |
| Vendor | F5 NGINX |
| Component | HTTP/2 |
| Vulnerability type | Integer overflow |
| Memory impact | Heap out-of-bounds write |
| Attack vector | Network |
| Authentication | Not required |
| CVSS 3.1 | 8.1 HIGH |
| CVSS 4.0 | 9.2 CRITICAL |
HTTP/2 uses flow-control windows to regulate how much data can be transmitted between endpoints.
CVE-2026-123007 involves improper handling of HTTP/2 flow-control window updates.
An attacker can manipulate these updates to trigger an integer overflow, potentially resulting in memory corruption.
Unauthenticated Remote Attacker
|
v
HTTP/2 Connection
|
v
Malicious Flow-Control
Updates
|
v
Integer Overflow
|
v
Heap Memory Corruption
|
v
Remote Code
Execution
|
v
NGINX Worker Privileges
|
v
Additional Privilege
Escalation Required
NGINX Open Source:
| Branch | Affected versions | Fixed version |
|---|---|---|
| Stable | 1.30.x before 1.30.7 | 1.30.7 |
| Mainline | 1.9.5β1.31.8 | 1.31.9 |
Important: The vulnerability requires HTTP/2 to be enabled on an affected listening port. Distribution packages may backport security patches without changing the upstream version number.
Check the installed NGINX version:
nginx -v
Inspect compilation options:
nginx -V 2>&1
Review the active configuration:
sudo nginx -T
Check HTTP/2 configuration:
sudo nginx -T 2>&1 | grep -i http2
Test configuration syntax:
sudo nginx -t
Review NGINX error logs:
sudo tail -f /var/log/nginx/error.log
Look for unexpected worker crashes and investigate suspicious process creation.
Stable branch:
sudo apt update
sudo apt upgrade nginx
Mainline branch:
Upgrade to NGINX 1.31.9 or later.
Verify the installed package and vendor security advisory before assuming that an upgrade command has installed the fix.
Disable HTTP/2 on exposed listeners where possible.
For modern NGINX configurations, remove the http2 parameter from the relevant listen directives.
Then test and reload:
sudo nginx -t
sudo nginx -s reload
β οΈ Disabling HTTP/2 is a temporary mitigation for this vulnerability, not a replacement for security updates.
| CVE | Component |
|---|---|
| CVE-2026-123007 | HTTP/2 flow control |
| CVE-2026-123633 | HTTP/2 |
| CVE-2026-123634 | DNS resolver |
| CVE-2026-121810 | HTTP/3 |
| CVE-2026-113425 | Mail proxy |
These vulnerabilities have different configuration requirements and should be assessed individually.
π’ SECURITY IS NOT OPTIONAL
Understand β’ Detect β’ Patch β’ Protect
NGINX2ROOT | CVE-2026-123007 | 2026