CVE-2026-123007: NGINX ngx_http_v2_module vulnerability
This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 37.3.0.1Fixed in 37.0.8.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.31.9Fixed in 1.30.7 - Upgrade
Upgrade
alpine/nginxto a version that resolves this vulnerability.Fixed in 1.28.3-r8 - Upgrade
Upgrade
alpine/nginxto a version that resolves this vulnerability.Fixed in 1.30.7-r0
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
NGINX Plus and NGINX Open Source deployments that use HTTP/2 are affected. The issue is in data-plane traffic handling and does not expose the control plane.
What access does an attacker need?
The vector is network-based and requires no privileges or user interaction. Exploitation requires processing specially crafted, undisclosed traffic that causes the HTTP/2 flow-control window to exceed its allowed threshold.
What is the likely impact if exploitation succeeds?
The typical result is an NGINX worker segmentation fault, which can disrupt service. The overflow can also corrupt memory; remote code execution may be possible where ASLR is disabled or can be bypassed.
How can I tell whether my deployment may be affected?
Determine whether the NGINX instance accepts or processes HTTP/2 traffic. Software versions that have reached End of Technical Support were not evaluated.