CVE-2026-121810: HTTP/3 (QUIC) connection draining when proxying
A use-after-free in nginx's HTTP/3 connection-draining logic when proxying to an upstream. Part of the NGINX2Root set disclosed by Xint; exploitation gives code execution as the nginx worker.
Executive Summary & Technical Impact
A use-after-free in nginx's HTTP/3 connection-draining logic when proxying to an upstream. Part of the NGINX2Root set disclosed by Xint; exploitation gives code execution as the nginx worker.
Tracked under CVE-2026-121810 (CWE-416 (Use After Free)), this vulnerability affects NGINX Open Source 1.25.0–1.31.8 and carries a severity score of 9.2 (CVSS 4.0) (CRITICAL). Engineering and security operations teams running NGINX Open Source should prioritize upgrading to NGINX Open Source 1.31.9 and 1.30.7.
Remediation & Patch Guidance
- Upgrade to nginx 1.31.9 or 1.30.7 and restart.
- If you cannot patch yet, consider disabling HTTP/3 (QUIC) listeners; turning off HTTP/2 alone does not help.
Frequently Asked Questions (CVE-2026-121810)
What versions are affected by CVE-2026-121810?
CVE-2026-121810 affects NGINX Open Source 1.25.0–1.31.8 in NGINX Open Source (HTTP/3 (QUIC) connection draining when proxying).
How do I patch or remediate CVE-2026-121810?
Upgrade affected deployments to NGINX Open Source 1.31.9 and 1.30.7 and verify the remediation steps listed above.
What is the CVSS score of CVE-2026-121810?
CVE-2026-121810 is rated CRITICAL with a CVSS score of 9.2 (CVSS 4.0) (vector: Network, unauthenticated. Requires HTTP/3 enabled with requests proxied to an upstream. Disabling HTTP/2 does not block this path.).
NGINX2Root: Five NGINX Memory-Safety Bugs, Two of Them Unauthenticated HTTP/2 RCE (CVE-2026-123007, CVE-2026-123633)
F5 shipped nginx 1.31.9 and 1.30.7 on November 18, 2026. The worst bug, an HTTP/2 flow-control integer underflow, has been in the code since nginx 1.9.5 in 2015 and was shown to give code execution on a server that only serves static files. Upgrade, then restart. A reload does not load the new binary.
Read full engineering post-mortem (6 min read) →