Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-121810: HTTP/3 Connection-Draining Use-After-Free in NGINX

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

CVE-2026-121810 is a use-after-free vulnerability in ngx_http_v3_module affecting NGINX Plus and NGINX Open Source configured for HTTP/3 over QUIC with upstream proxying. When a worker has insufficient free connections, an active QUIC connection can be prematurely closed during new-stream creation and backend request forwarding, resulting in use of freed memory. A remote, unauthenticated attacker can trigger a worker-process crash and restart; arbitrary code execution is possible if ASLR is disabled or bypassed. Exploitation also depends on conditions outside the attacker's control. Affected upstream Open Source versions are 1.25.0 through 1.30.6 and 1.31.0 through 1.31.8, excluding vendor-backported fixes. The vulnerability affects only the data plane, with no control-plane exposure.

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.

Exploitation can crash and restart NGINX worker processes, interrupting connections and causing denial of service. Successful code execution runs with the worker process's privileges and may expose worker-accessible application data or credentials, permit request manipulation, or disrupt backend services. Root access and container escape are not inherent consequences and would require a separate vulnerability or additional privileges.

Mitigation

If you can’t patch tonight, do this now.

If patching must be deferred, disable HTTP/3 and remove QUIC listeners on affected endpoints, clear HTTP/3 Alt-Svc advertisements, and ensure existing vulnerable worker connections have ended. Disabling HTTP/2 does not mitigate this vulnerability. Retain ASLR as defense in depth, but do not treat it as a complete mitigation because bypasses may be possible. Monitor unexpected worker crashes and suspicious worker child processes or outbound connections. F5's individual advisory lists no interim workaround; disabling HTTP/3 is a feature-removal measure.

Remediation

Patch, then assume compromise.

Upgrade NGINX Open Source to 1.30.7 or 1.31.9, or a later fixed release in the applicable branch. Upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1, or a later fixed release in the applicable branch. No fixed release is listed for Plus R34–R36; migrate to a supported release containing the fix. Distribution packages may contain backported fixes, so verify the full package revision against the distribution advisory. Update bundled deployments and container images separately. Fully restart NGINX after upgrading and verify that the updated executable is running and previous workers have terminated.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-121810The repository contains eight files: a Python attack script, a Python slow-response backend, two Dockerfiles, a Docker Compose definition, an nginx configuration, a dependency manifest, and a README. It is a standalone crash-trigger PoC and reproducible lab, not a framework module. No repository URL, git reference, or archive size was supplied; the listed file sizes total 10,659 bytes, while repo.size_bytes is left at 0 as an unknown placeholder. The intended mechanism is unauthenticated QUIC connection exhaustion against nginx with outstanding proxied HTTP/3 streams. The lab limits nginx to one worker and 24 connection slots. The backend immediately serves /health but delays other requests for three seconds before returning 64 KiB. The script attempts repeated waves of concurrent sessions and interprets failed HTTP health checks as worker crashes. It contains no RCE implementation or exfiltration behavior. Significant implementation defects undermine the PoC: aioquic.asyncio.connect yields a QuicConnectionProtocol, but the script passes that protocol to H3Connection, which expects the underlying QuicConnection. It also calls get_next_available_stream_id on the protocol rather than its underlying connection. No explicit transmission after queuing headers or HTTP/3 event integration is provided. Consequently, session exceptions may be collected and printed without the intended HTTP/3 load being generated. Context-manager exit performs normal connection closure rather than demonstrating the abrupt teardown claimed in the documentation. Failed health probes alone do not establish a use-after-free, and nginx worker restarts can also escape detection. The README claims CVE-2026-121810 affects nginx 1.25.0–1.31.8 and is fixed in 1.30.7/1.31.9, but no patch, crash trace, sanitizer output, or independently verified advisory is supplied. Its broad affected range overlaps a claimed fixed release, and its CVSS score and vector are inconsistent. CVE-2026-123633 is mentioned only as a purported related HTTP/2 issue, not implemented as a target. The CVE, affected versions, and RCE assertions therefore remain unverified. The Dockerfile's rm -rf command only removes package-manager cache and is not evidence of a malicious fake exploit.LLCForge · Disclosed Nov 18, 2026 · python · dockerfile · networkPoC
FAQ

Frequently asked questions

Is CVE-2026-121810 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-121810 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-121810?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-121810, the earliest disclosed Nov 18, 2026.
Is there a patch for CVE-2026-121810?
Upgrade NGINX Open Source to 1.30.7 or 1.31.9, or a later fixed release in the applicable branch. Upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1, or a later fixed release in the applicable branch.
How severe is CVE-2026-121810?
CVE-2026-121810 has a CVSS v4 score of 9.2 (Critical) as of Nov 19, 2026.
Activity feed

Recent activity

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

View more in app →
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 affecting HTTP/3 (QUIC) and processing of requests forwarded to backend servers. It belongs to the five critical vulnerabilities collectively called NGINX2Root, which the advisory describes as potentially allowing unauthenticated remote code execution with worker-process privileges. Recommended protections include installing patched releases and reviewing or temporarily restricting HTTP/3 functionality. Disabling HTTP/2 does not protect against this flaw.Read more ↗malware newsNews · Nov 19, 2026NGINX2Root: What NGINX Admins Should Know - Malware News - Malware Analysis, News and IndicatorsAn NGINX2Root use-after-free vulnerability in HTTP/3 connection draining, affecting upstream versions 1.25.0 through 1.31.8 when proxying to a backend while the worker is short of free connections. The article describes potential unauthenticated code execution with worker privileges and assigns F5's CVSS v4.0 score of 9.2. Fixed releases include NGINX Open Source 1.30.7 and 1.31.9 and NGINX Plus 37.0.8.1 and 37.3.0.1. Temporary mitigation consists of removing QUIC listeners, disabling HTTP/3 and clearing advertised HTTP/3 availability. No public exploit code or in-the-wild exploitation was reported as of November 19, 2026.Read more ↗cert seNews · Nov 19, 2026Allvarliga sårbarheter i NGNIX - CERT-SEOne of five NGINX vulnerabilities rated CVSS 8.1 that can allow an unauthenticated attacker to execute code remotely with NGINX worker-process privileges. CERT-SE recommends updating when version 1.31.9 is released, prioritizing internet-facing instances. No vulnerability-specific workaround is described.Read more ↗socradar blogNews · Nov 19, 2026NGINX2Root: What NGINX Admins Should KnowAn NGINX HTTP/3 QUIC connection-draining use-after-free affecting versions 1.25.0–1.31.8 when HTTP/3 proxies to a backend and the worker is short of free connections. It belongs to the NGINX2Root set, which can enable unauthenticated worker-process code execution. F5 assigns CVSS v4.0 severity 9.2. No public exploit code or in-the-wild exploitation was reported. Fixed in NGINX Open Source 1.30.7 and 1.31.9 and NGINX Plus 37.0.8.1 and 37.3.0.1. Temporary mitigation is to remove QUIC listeners, disable HTTP/3, and clear the Alt-Svc advertisement.Read more ↗
+50 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 activity18Community discussion across Reddit, Mastodon, and other social sources.