Critical NGINX HTTP/2 flaws allow unauthenticated remote code execution
Both flaws need HTTP/2 enabled; CVE-2026-123007 dates to NGINX 1.9.5 in 2015, and F5’s fixes shipped November 18.
HTTP/2 heap buffer overflow in NGINX Plus and Open Source
NGINX Plus and NGINX Open Source configurations that use HTTP/2 can hit a heap buffer overflow when the flow-control window exceeds its allowed threshold while processing certain traffic. A remote attacker needs no account and no user interaction. The usual result is an NGINX worker crash and memory corruption; code execution is possible if ASLR is off or bypassed. This is a data-plane issue only. Affected and fixed versions are not listed.
What to do: Apply F5's update for CVE-2026-123007. No workaround is stated.
| Product | Affected |
|---|---|
| F5 NGINX Plus | — |
| F5 NGINX Open Source | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Both flaws need HTTP/2 enabled; CVE-2026-123007 dates to NGINX 1.9.5 in 2015, and F5’s fixes shipped November 18.
F5 fixed the issues in NGINX Open Source 1.30.7 and 1.31.9; Xint cites proven exploits but no confirmed attacks.
Xint says HTTP/2 CVE-2026-123007 hits every release from 1.9.5 through 1.31.8, with 1.31.9 not yet available.
Fixes are in Open Source 1.30.7 and 1.31.9; Wiz showed code execution, but production attacks are not confirmed.
Researchers demonstrated CVE-2026-123007; CERT-EU reports no in-the-wild exploitation and urges internet-facing updates first.
Rapid7's proof of concept needs roughly 128 GB of HTTP/2 data and a specific glibc memcpy path.
The page lists five CVE IDs and links a fix guide, but gives no versions or exploitation status.
Today 2.2K readers · 2.4K views · 127 reads · all time 206K views