CVE-2026-121810: HTTP/3 Connection-Draining Use-After-Free in NGINX
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.
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.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.
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.
Recent activity
86 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.