CVE-2026-123633: HTTP/2 Connection-Draining Use-After-Free in NGINX
CVE-2026-123633 is a use-after-free vulnerability in the ngx_http_v2_module component of NGINX Open Source and NGINX Plus. It affects configurations accepting HTTP/2 client connections and proxying requests to backend servers when a worker is running low on available worker_connections. An HTTP/2 connection can incorrectly remain on the reusable-connection list after request processing begins. Under connection-slot pressure, ngx_drain_connections() can close that active connection, freeing HTTP/2 memory still referenced by request-processing code. A specially crafted request can consequently cause worker-process memory corruption, denial of service, or potentially arbitrary code execution. The issue affects the data plane only, with no control-plane exposure. Affected upstream releases begin at 1.19.7 and extend through 1.31.8, excluding fixed branch releases such as 1.30.7.
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 cause NGINX worker crashes and denial of service. Successful exploitation can also execute arbitrary code with NGINX worker-process privileges if ASLR is disabled or bypassed; researchers demonstrated code execution with an ASLR bypass in laboratory environments. Depending on worker permissions, compromise could expose accessible application data and credentials, permit traffic tampering, and disrupt multiple applications sharing the proxy. The vulnerability does not inherently grant root privileges or container escape; those outcomes require additional vulnerabilities or privileges.
Mitigation
If you can’t patch tonight, do this now.
If patching must be delayed, temporarily disable HTTP/2 on affected listeners using 'http2 off;' where supported and remove the legacy 'http2' parameter from listen directives as applicable. Reload the configuration, ensure old workers have exited, and verify that affected endpoints no longer accept HTTP/2. Test compatibility because gRPC and other HTTP/2-dependent services may be disrupted. Retain ASLR, but do not rely on it as a complete defense because bypasses have been demonstrated. Increasing worker_connections does not correct the underlying use-after-free.
Remediation
Patch, then assume compromise.
Upgrade NGINX Open Source to stable version 1.30.7, mainline version 1.31.9, or a later fixed release. For NGINX Plus, install 37.0.7.1 or 37.2.0.1 for the applicable branch, or a later vendor-recommended fixed build. Affected R34–R36 deployments should migrate to a release containing the fix. For distribution packages, embedded products, and container images, install the supplier's corrected build and account for backported fixes rather than relying solely on upstream version numbers. Fully restart NGINX or perform a supported live binary upgrade, ensuring all vulnerable workers have exited; a configuration reload alone does not replace the executable.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 8 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2026-123633 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-123633 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123633?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-123633, the earliest disclosed Nov 18, 2026.
- Is there a patch for CVE-2026-123633?
- Upgrade NGINX Open Source to stable version 1.30.7, mainline version 1.31.9, or a later fixed release. For NGINX Plus, install 37.0.7.1 or 37.2.0.1 for the applicable branch, or a later vendor-recommended fixed build.
- How severe is CVE-2026-123633?
- CVE-2026-123633 has a CVSS v4 score of 9.2 (Critical) as of Nov 19, 2026.
Recent activity
297 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.