Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-123633: HTTP/2 Connection-Draining Use-After-Free in NGINX

Published Nov 18, 2026 · Updated today
Trending this week#3of 430,159 vulnerabilities
Mention activity · 30 daysAt least 200 mentions · peak 114 in a dayToday
CVSS9.2Critical · v4
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-123633CWE-416 · Use After Free

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 8 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-123633The seven-file repository contains a standalone Python attack script, a Python delayed-response backend, two Dockerfiles, Docker Compose configuration, nginx configuration, and a README. poc.py manually constructs HTTP/2 frames using only the standard library, creates concurrent TLS connections, requests /slow, and immediately sends stream cancellations followed by abortive socket closes. The lab publishes nginx ports 8443 and 8080 and deliberately limits a single worker to 24 connection slots. The backend exposes delayed /slow and immediate /fast responses. This is an active denial-of-service attempt, not merely a detection script. Its basic disruption payload is implemented, but successful exploitation is not demonstrated by the supplied evidence. A failed health check can reflect temporary resource exhaustion rather than a worker crash, and nginx worker restarts could also hide a crash. The client performs minimal HTTP/2 response parsing, does not verify negotiated ALPN, and sends request HEADERS without END_STREAM, introducing additional uncertainty about protocol handling and upstream timing. No heap manipulation, memory disclosure, or RCE payload supports the README's speculative code-execution claim. Documentation and implementation differ: the actual options are --wave-size, --waves, --host, --port, --no-rst, and --health-port; the README advertises unsupported --streams and --verbose options and gives different defaults. The asserted CVE, affected range, fixes, and relationship to CVE-2026-121810 are repository claims rather than independently established facts; the latter CVE is only a reference, not an implemented target. No exfiltration or attacker callback endpoint is present. The Dockerfile's removal of package-manager lists is routine image cleanup, not evidence of a destructive fake exploit. Repository URL, git reference, and archive size were not provided; empty strings and zero represent unavailable metadata.LLCForge · Disclosed Nov 18, 2026 · python · dockerfile · networkOperationalnginx-exploitsThe repository contains two Markdown documents and two standalone Python CLI programs. The root README indexes the claimed vulnerabilities; the nested README describes mechanisms, affected releases, usage, and mitigations. exploit.py identifies itself as version 2.2.1 and includes reverse-shell templates, post-exploitation command definitions, threaded target handling, resume support, and JSON/JSONL reporting. poc.py identifies itself as version 2.1.0 and is presented as a detection tool, with explicit version-range tables, threaded scanning, retries, and structured results. Visible imports are Python standard-library modules; no framework integration is evident. The documentation alleges an unauthenticated HTTP/2 UAF involving incomplete HEADERS and connection draining, plus a send_window arithmetic flaw involving stream cancellation and WINDOW_UPDATE traffic leading to TLS-path out-of-bounds access. Both scripts define HTTP/2 frame constants and the standard connection preface. However, their central networking, detection, and exploitation routines are omitted by truncation. Consequently, the supplied excerpts establish exploit intent and payload availability, not a working RCE chain, reliable detection, or authenticity of the CVE/version/patch claims. A visible default handler-offset description references NGINX 1.18.0, outside the documented UAF range, indicating a target-layout assumption requiring further scrutiny. The repository is not detection-only because it includes an exploitation program and shell payloads. OPERATIONAL denotes the presence of basic payload definitions, not independently verified exploit reliability. No affirmative evidence establishes that it is fake; likewise, the available material cannot establish validity. The /tmp/f removal belongs to a conventional FIFO shell template rather than broad destructive behavior. No fixed command-and-control or exfiltration server is visible. Documentation badges, author links, and example addresses are not observed runtime destinations. The original repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata. Listed file sizes sum to 84,234 bytes, which is not an archive-size measurement.Ghost-Bx1 · Disclosed Nov 18, 2026 · python · networkOperational
FAQ

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.
Activity feed

Recent activity

297 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
si cert blogNews · Nov 19, 2026SI-CERT 2026-09 / Kritične ranljivosti v spletnem strežniku NGINX - nginx2root - SI CERTA use-after-free vulnerability in NGINX HTTP/2 connection processing and backend-server connections. The affected configuration uses HTTP/2 with requests forwarded to a backend server. The advisory describes possible arbitrary code execution with NGINX worker-process privileges, depending on version and configuration. It belongs to the NGINX2Root group. Fixed NGINX Open Source releases are 1.30.7 and 1.31.9; disabling HTTP/2 is a temporary mitigation.Read more ↗hackreadNews · Nov 19, 2026F5 Patches Two NGINX HTTP/2 Vulnerabilities, One Dating Back to 2015A use-after-free vulnerability in NGINX HTTP/2 processing affecting versions 1.19.7 through 1.31.8. It occurs during reverse-proxy processing when available connection slots run low and can allow unauthenticated remote code execution. HTTP/2 must be enabled. Fixes are available in NGINX Open Source 1.30.7 and 1.31.9 and applicable NGINX Plus releases. Temporarily disabling HTTP/2 is a workaround.Read more ↗socprime blogNews · Nov 19, 2026CVE-2026-123633: Critical NGINX HTTP/2 RCEA critical use-after-free vulnerability in NGINX HTTP/2 connection management, rated CVSS v4.0 9.2. Exploitation requires direct HTTP/2 access, reverse-proxy processing, and scarce worker connection slots. Incorrect connection reuse tracking allows an active connection to be freed during upstream connection establishment, causing worker crashes or potentially arbitrary code execution with NGINX worker privileges. Researchers demonstrated working remote code execution and an ASLR bypass; working private exploits exist, but public PoC claims are not independently validated. No confirmed real-world exploitation was reported as of November 19, 2026. Fixed Open Source releases are 1.30.7 and 1.31.9; fixed NGINX Plus releases are 37.0.7.1 and 37.2.0.1. Administrators should restart or appropriately upgrade running binaries after patching. Temporarily disabling HTTP/2 blocks the known attack path; raising worker_connections alone does not fix the vulnerability.Read more ↗ncsc huNews · Nov 19, 2026Riasztás az NGINX kritikus sérülékenységeiről - Nemzeti Kiberbiztonsági IntézetAn NGINX use-after-free vulnerability involving HTTP/2 connections and requests forwarded to backend servers. It is one of the five critical NGINX2Root vulnerabilities described as potentially enabling unauthenticated remote code execution with worker-process privileges. The advisory recommends patched NGINX releases or distribution security updates and explicitly states that temporarily disabling HTTP/2 prevents exploitation of this vulnerability at the affected endpoints.Read more ↗
+35 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity154Community discussion across Reddit, Mastodon, and other social sources.