CVE-2026-123007: NGINX HTTP/2 Flow-Control Integer Underflow and Remote Code Execution
CVE-2026-123007 is an integer-underflow vulnerability in ngx_http_v2_module affecting HTTP/2-enabled NGINX Open Source and NGINX Plus deployments. Cancellation of an HTTP/2 stream can restore unused sending credit without enforcing the connection flow-control window's protocol maximum. Subsequent WINDOW_UPDATE bounds checking can underflow, allowing an invalid send-window value that ultimately becomes an unsafe memory-copy length in buffered output processing. This can cause out-of-bounds heap reads and writes, worker segmentation faults, and potentially remote code execution. The vulnerable functionality originated in NGINX 1.9.5; affected upstream releases include versions through 1.30.6 and mainline 1.31.0–1.31.8, unless separately patched. Static-file servers are affected; reverse proxying and third-party modules are not required. The vulnerability is part of the NGINX2Root group and affects the data plane, not the control plane.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Unauthenticated remote attackers can crash NGINX worker processes, corrupt worker memory, potentially disclose process memory, and execute arbitrary code when ASLR is disabled or bypassed. Successful code execution occurs with NGINX worker-process privileges, potentially exposing accessible application data and credentials, enabling response modification, or disrupting multiple applications sharing the instance. Root access and container escape are not inherent consequences; demonstrated escalation chains require a separate Linux kernel vulnerability.
Mitigation
If you can’t patch tonight, do this now.
If patching is delayed, disable HTTP/2 on every affected listener by setting 'http2 off;' where supported and removing the legacy 'http2' parameter from listen directives. Apply the configuration, ensure old workers have exited, and verify that affected endpoints no longer accept HTTP/2, including directly reachable origins behind intermediaries. Test compatibility because gRPC and other HTTP/2-dependent services may fail. HTTP/2 termination at a CDN or proxy may disrupt particular exploit implementations but is not a reliable substitute for patching. Retain ASLR, restrict worker privileges and network access, and monitor for worker crashes, unusually large or long-lived HTTP/2 sessions, and unexpected worker-launched processes.
Remediation
Patch, then assume compromise.
Upgrade NGINX Open Source to stable 1.30.7, mainline 1.31.9, or a later fixed release. Upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1, as appropriate for the release line; affected older branches without a fixed build must migrate to a supported fixed release. For distribution packages, embedded products, and container images, install the supplier's corrected packages or images and account for backported fixes rather than relying solely on upstream version strings. Fully restart NGINX or perform an appropriate live binary upgrade, and verify that the patched executable is running and vulnerable workers have exited. A configuration reload alone does not replace the executable.
Exploits
5 exploits validated by Mallory's analysis. Hidden: 13 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2026-123007 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-123007 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123007?
- Yes. Mallory tracks 5 public exploits or proofs of concept for CVE-2026-123007, the earliest disclosed Nov 18, 2026.
- Is there a patch for CVE-2026-123007?
- Upgrade NGINX Open Source to stable 1.30.7, mainline 1.31.9, or a later fixed release. Upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1, as appropriate for the release line; affected older branches without a fixed build must migrate to a supported fixed release.
- How severe is CVE-2026-123007?
- CVE-2026-123007 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 6.4% (94th percentile) as of Nov 19, 2026.
Recent activity
446 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.