NGINX HTTP/2 heap overflow, potential RCE

Critical 9.2 CVE-2026-123007

High risk · public exploit

Severity 9.2 Reach 10.0 Ease 3.0 Exploitation 2.0 Tooling 10.0

Risk assessment

NGINX HTTP/2 heap overflow (CVSS 9.2) lets attackers crash workers or possibly execute code with ASLR off. Apply the vendor HTTP/2 fix or disable HTTP/2.

By Yazoul AI · automated

What to do

Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.

Exploitation confirmed - public proof-of-concept - CVE-2026-123007 is a critical heap buffer overflow in NGINX Plus and NGINX Open Source configurations using HTTP/2 that lets remote attackers crash worker processes, corrupt memory, or potentially execute code. Disable HTTP/2 or apply the vendor fix immediately.

Overview

CVE-2026-123007 affects NGINX Plus and NGINX Open Source deployments that handle HTTP/2 traffic. When the server processes undisclosed traffic patterns, the HTTP/2 flow control window can grow beyond the allowed threshold, causing a heap buffer overflow. In practice, the overflow is typically followed by a segmentation fault that takes down the NGINX worker process.

The bug has a CVSS score of 9.2 (critical). The attack vector is network-based, requires no privileges, and needs no user interaction. The high complexity rating reflects the effort needed to reliably shape the overflow, but a determined attacker can work that out.

Only the data plane is exposed. There is no control plane exposure, so management interfaces are not directly at risk from this issue.

Impact

An attacker who reaches an affected server over HTTP/2 can do three things:

  • Crash the worker process. Repeated overflows cause repeated crashes, which degrades availability and can take the service offline.
  • Corrupt memory. A successful overflow overwrites adjacent heap data, which can lead to unpredictable behavior or secondary faults.
  • Potentially execute code remotely. On systems with Address Space Layout Randomization (ASLR) disabled, or where the attacker can bypass ASLR, a well-crafted exploit can achieve arbitrary code execution.

Because the vulnerability needs no authentication, any exposed HTTP/2 endpoint is a candidate target. Internet-facing servers and load balancers are the highest-risk assets.

There is no confirmed report of this vulnerability being exploited in the wild as of publication. The EPSS score of 6.4% indicates a moderate probability of exploitation within 30 days, so treat it as a live risk rather than a theoretical one.

Remediation and Mitigation

Apply these steps in order of preference:

  1. Patch. Upgrade to the fixed NGINX Plus or NGINX Open Source release listed in the vendor advisory. Versions past End of Technical Support (EoTS) are not evaluated and will not receive a fix, so plan to upgrade off those branches.
  2. Disable HTTP/2 if you cannot patch immediately. Set http2 off in your server blocks and fall back to HTTP/1.1. This removes the attack surface entirely.
  3. Confirm ASLR is enabled. On Linux, check /proc/sys/kernel/randomize_va_space and make sure it is set to 2. ASLR does not fix the bug, but it makes code execution much harder.
  4. Restrict exposure. Put rate limiting and connection limits in front of HTTP/2 endpoints, and limit access to trusted networks where possible.
  5. Monitor. Watch for repeated worker segmentation faults or unexpected restarts in logs. These can signal an attempted or successful exploit.

Check breach reports for incident data and security news for vendor updates related to this issue.

Security Insight

HTTP/2 implementation bugs have become a recurring source of memory safety failures in reverse proxies and web servers, because the protocol’s flow control and HPACK state are subtle and easy to get wrong under concurrency. NGINX’s long track record of stability makes this severity-9.2 event notable: the fact that a heap overflow survived into shipping code in a core protocol handler suggests that fuzzing around the flow control window is still an under-tested area. Operators should treat HTTP/2 support as a security-sensitive feature that needs explicit hardening, not a default to switch on and forget.

Further Reading

Exploit references 12 PoC Show

Public PoC References

Unverified third-party code

These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).

Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.

Repository Stars
sfewer-r7/CVE-2026-123007

Proof-of-concept (PoC) scripts for CVE-2026-123007, an integer underflow in NGINX HTTP/2.

★ 223
arkrwn/NGINX2Root-CVE-2026-123007

Research Note: Turning Public Intelligence into a Root Exploit (Case Study: CVE-2026-123007)

★ 5
WormW/nginx2root-rce-lab

CVE-2026-123007(nginx2root)RCE 复现 + 未标定 nginx 版本标定工具

★ 2
akarkode/nginx-http2-cve-2026-123007-lab

Local lab for CVE-2026-123007 (nginx HTTP/2 integer underflow): vulnerable Docker container + proof-of-concept

★ 2
LLCForge/CVE-2026-123007

CVE-2026-123007 — nginx HTTP/2 flow-control integer underflow → heap OOB write. CVSS 8.1. Affects nginx 1.9.5–1.31.8. Docker PoC.

★ 1

Showing 5 of 12 known references. Source: nomi-sec/PoC-in-GitHub.

Share

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.