CVE-2026-121810: NGINX ngx_http_v3_module vulnerability
Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3. A remote, unauthenticated attacker can cause a use-after-free condition in the NGINX worker process, leading to a restart. Exploitation also depends on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 37.3.0.1Fixed in 37.0.8.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.31.9Fixed in 1.30.7
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
NGINX Plus and NGINX Open Source deployments that use HTTP/3 are affected. The issue is limited to the data plane; there is no control plane exposure.
Does exploitation require credentials or user interaction?
No. A remote attacker can target the affected worker process without authentication or user interaction, although successful exploitation depends on conditions beyond the attacker’s control.
What is the practical difference between the denial-of-service and code-execution risks?
The use-after-free can cause an NGINX worker process restart, resulting in denial of service. Code execution is additionally associated with systems where ASLR is disabled or where an attacker can bypass ASLR.