Introduction
An ordering mistake in the way NGINX creates QUIC streams allows a remote, unauthenticated attacker to free a connection that is still in use. That restarts the worker process and, under narrower conditions, opens a path toward code execution. With W3Techs attributing 29.8 percent of websites with an identifiable web server to NGINX, every deployment that has turned on HTTP/3 has reason to check its version against F5's advisory.
F5 published advisory K000163927 on November 18, 2026. It rates CVE-2026-121810 as High under CVSS 3.1 (8.1) and Critical under CVSS 4.0 (9.2). Both vectors specify network access, high attack complexity, no privileges required, and no user interaction. F5 classifies the bug as CWE-416 (use after free) in ngx_http_v3_module, notes that it affects the data plane only with no control-plane exposure, and credits Xint.io with reporting it through coordinated disclosure.
As for exploitation status, the sources we reviewed do not identify a threat actor or report confirmed in-the-wild exploitation, and the reviewed CISA Known Exploited Vulnerabilities catalog excerpt does not list this CVE. That absence is not proof that exploitation has not occurred.
Technical information
Background: reusable connections
In nginx, a connection marked reusable is one the worker may close ("drain") when it runs low on free connection slots. A QUIC connection should only be reusable when it has no active streams. Whether a QUIC connection still has streams is determined by the per-connection stream tree, qc->streams.tree.
Root cause
Before the fix, ngx_quic_create_stream() in src/event/quic/ngx_event_quic_streams.c performed these operations in this order:
- Saved the main connection's
reusableflag, then cleared it withngx_reusable_connection(c, 0). - Called
ngx_get_connection()to obtain a connection slot for the new stream. - Only at the very end, added the new stream to
qc->streams.tree.
The problem lies in step 2. If the worker was short on free connections, the drain logic inside ngx_get_connection() could close an idle stream belonging to the same QUIC connection. Because the stream being created was not yet in the tree, closing that sibling left the tree empty, and the main QUIC connection was marked reusable again. From that point on, nginx treated a busy connection as idle.
A later drain, for example when the request opens a connection to an upstream, could then free the QUIC connection while one of its streams was still using it. That is the use after free.
Attack flow
Based on the upstream commit message and F5's advisory, the sequence looks like this:
- The attacker reaches an NGINX server configured for HTTP/3. No authentication is required.
- On a single QUIC connection, there is at least one idle stream while a new stream is being created.
- The worker is low on free connection slots at the moment
ngx_get_connection()runs, so the drain path closes the idle sibling stream. - With the new stream not yet registered in
qc->streams.tree, the QUIC connection appears to have no streams and is marked reusable. - A subsequent drain (for example, triggered when the request opens an upstream connection) frees the QUIC connection while the new stream still references it.
- The worker process operates on freed memory and restarts, producing a denial of service.
Step 3 depends on worker connection pressure. That matches F5's statement that exploitation depends on conditions beyond the attacker's control, and the high attack complexity in both CVSS vectors.
Impact conditions
The direct, stated consequence is a worker restart and possible denial of service. F5 also states that code execution may be possible on systems where Address Space Layout Randomization (ASLR) is disabled, or where the attacker can bypass ASLR. That impact is conditional. It does not show that code execution is achievable on every affected server. The advisory provides no public exploit, request details, or reproducible procedure.
Patch information
F5 shipped the fix on November 18, 2026 in NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable), and in NGINX Plus 37.3.0.1 and 37.0.8.1. F5 tracks the issue internally as NPS-370. The nginx.org security advisories page marks 1.31.9+ and 1.30.7+ as not vulnerable, and the 1.31.9 release notes list the "use after free in HTTP/3 (CVE-2026-121810)" among the ten issues fixed in that release.
The upstream commit
The fix is a single small commit by Roman Arutyunyan, credited "Reported by Xint.io", titled "QUIC: avoid main connection reuse after creating a stream". The same change appears twice in nginx/nginx with the same message and diff:
c58d2a22d12350766185c94f2245bf4be5bcfb7d, committed by Sergey Kandaurovb5252dae1ca0d4c516b8bcffd9fa7fd967b73075, committed by Arutyunyan
The two commits have different parents, so they were most likely applied to two branches (mainline and stable). We did not confirm which branch each one is on. Both touch only src/event/quic/ngx_event_quic_streams.c, with 4 lines added and 2 removed.
@@ -731,12 +731,15 @@ ngx_quic_create_stream(ngx_connection_t *c, uint64_t id) addr_text.data = NULL; } + ngx_rbtree_insert(&qc->streams.tree, &qs->node); + reusable = c->reusable; ngx_reusable_connection(c, 0); sc = ngx_get_connection(c->fd, log); if (sc == NULL) { ngx_destroy_pool(pool); + ngx_rbtree_delete(&qc->streams.tree, &qs->node); ngx_queue_insert_tail(&qc->streams.free, &qs->queue); ngx_reusable_connection(c, reusable); return NULL; @@ -803,6 +806,7 @@ ngx_quic_create_stream(ngx_connection_t *c, uint64_t id) if (cln == NULL) { ngx_close_connection(sc); ngx_destroy_pool(pool); + ngx_rbtree_delete(&qc->streams.tree, &qs->node); ngx_queue_insert_tail(&qc->streams.free, &qs->queue); ngx_reusable_connection(c, reusable); return NULL; @@ -811,8 +815,6 @@ ngx_quic_create_stream(ngx_connection_t *c, uint64_t id) cln->handler = ngx_quic_stream_cleanup_handler; cln->data = sc; - ngx_rbtree_insert(&qc->streams.tree, &qs->node); - return qs; }
Reading the diff
- First hunk:
ngx_rbtree_insert()now runs beforengx_get_connection(), so the stream is registered before anything that can trigger a drain. This is the core of the fix. If a drain now closes a sibling stream, the tree still holds the new stream, the connection does not look idle, and it is not marked reusable. - Second and third hunks: these keep the error paths consistent. If
ngx_get_connection()fails, or the cleanup handler cannot be allocated, the code now callsngx_rbtree_delete()before returning the stream to the free list, then restores the savedreusablestate as before. Without this, a stream back on the free list would remain in the lookup tree. - Last hunk: the old insertion just before
return qs;is removed, so a stream is never inserted twice.
The change is a narrow ordering fix, with no new locking or reference counting. It ensures that the "does this connection still have streams?" check always counts a stream that is still being created.
Upgrade guidance from F5
- F5 states that installing a version listed in its fixes column eliminates the vulnerability, and that a later version in the same branch should already contain the fix.
- If the advisory does not list a fixed release for your branch, F5 recommends upgrading to a version that has the fix.
- F5 lists no separate mitigation and does not recommend a temporary configuration change. Disabling HTTP/3 or any other workaround should not be treated as vendor-confirmed guidance.
- If your distribution backports fixes into its own nginx package, check specifically for this reordering of
ngx_quic_create_stream(). A build is only fixed if it includes this change.
Affected systems and versions
The vulnerable feature is ngx_http_v3_module, and only configurations using HTTP/3 are affected.
NGINX Open Source
- Affected: 1.31.0 through 1.31.8, and 1.25.0 through 1.30.6
- Fixed: 1.31.9 (mainline) and 1.30.7 (stable)
NGINX Plus
- Affected: 37.1.0 through 37.2.0.1, and 37.0.0 through 37.0.7.1
- Fixed: 37.3.0.1 and 37.0.8.1
F5 evaluates only versions that have not reached End of Technical Support, so the advisory does not establish the status of unsupported releases. Confirm your branch and release against the advisory instead of assuming an older release is safe.
F5 lists a number of other products as not vulnerable, including NGINX products other than those specified above, F5 AI Gateway, F5 Insight, and F5OS variants. At the time of the advisory, F5 Distributed Cloud and NGINX One Console were still under investigation, so their status was not confirmed.
References
- NVD entry for CVE-2026-121810
- CVE Record: CVE-2026-121810
- F5 advisory K000163927: NGINX ngx_http_v3_module vulnerability CVE-2026-121810
- nginx security advisories
- Upstream commit c58d2a22d12350766185c94f2245bf4be5bcfb7d
- Upstream commit b5252da
- nginx 1.31.9 release notes
- CISA Known Exploited Vulnerabilities Catalog
- W3Techs: Usage Statistics and Market Share of Nginx, November 2026
- F5 Completes Acquisition of NGINX
- NGINX Is Now Officially Part of F5
- F5 Company page



