Backports and Version Claims for CVE-2026-121810
An NGINX version string is a starting clue, not a patch receipt. CVE-2026-121810 affects official Open Source releases 1.25.0 through 1.31.8, but distributions may retain an older-looking version while carrying a backported security fix. Container images may show the inverse: a current tag that still contains an old binary layer. Accurate assurance needs package and process evidence.
Vulnerability overview
F5 published CVE-2026-121810 on November 18, 2026. It is a use-after-free in HTTP/3 stream handling, CWE-416, with CVSS 3.1 score 8.1 and high attack complexity. The NGINX advisory labels it medium severity. The upstream fixes are 1.30.7 and 1.31.9; NGINX Plus branches include 37.0.0 before 37.0.8.1, 37.1.0 before 37.3.0.1, and R34 through R36.
No confirmed in-the-wild exploitation or KEV entry was reported in the public advisory material at publication.
Mechanism and exploitation conditions
HTTP/3 request streams are children of a QUIC connection and consume worker connection slots. During stream creation, NGINX protects the parent from drain by removing it from a reusable queue. The new stream is not in the parent's tree until after the slot allocation. An idle sibling can close during that interval, cause the shutdown check to miss the in-progress stream, and requeue the parent.
The request's upstream connect then allocates another slot and can drain the parent. NGINX frees the request pool while the connection routine still holds an upstream pointer. Xint demonstrated worker-privilege code execution using HTTP/3 proxying and a controlled listener. The vendor notes that more conditions must align than the version range alone.
Impact
The issue can crash or restart workers, interrupting service and obscuring the trigger in ordinary request logs. Successful exploitation can execute code with the worker's rights and expose backend paths or local configuration. The CVE does not itself establish root or control-plane compromise.
Affected products and scope
The affected scope is a vulnerable binary with HTTP/3 and an upstream proxy path. Backports can make a reported version safe, while an unpatched fork or stale container layer can keep it vulnerable. A fixed upstream version may also be present in an image that is not the process actually serving traffic.
For package assurance, record the full package version, vendor advisory, binary hash, container digest, and process start time. Inspect the effective configuration for QUIC listeners and upstream behavior. Verify IPv4 and IPv6 reachability separately.
Exposure context
The selected ZoomEye Search app="NGINX" returned 316,219,992 product fingerprints. The CVE Filter returned 0. Exposure is 316,219,992 under the maximum-count rule.
That figure is not a version report and cannot resolve backports. It is useful for identifying a large product surface, but remediation evidence must come from the owned package and running process.
Remediation and mitigations
Install a fixed package or vendor backport and restart or live-upgrade the executable. Verify that worker processes use the new binary, not merely that the package database changed. For containers, rebuild the image, pin the package layer, and confirm the digest that runs in production.
If a patch cannot be deployed immediately, disable HTTP/3 by removing QUIC listeners and setting http3 off. Clear Alt-Svc and verify the effective socket state. A firewall can reduce reachability, but it is a containment layer and may not cover every network path.
Document the advisory mapping and retain the exact evidence used to approve closure. Re-check after rollbacks, base-image refreshes, or configuration imports because these operations can reintroduce an old binary or listener. A version string without package and process proof should remain an open assurance question.