CVE-2026-121810: NGINX ngx_http_v3_module vulnerability

Published Nov 18, 2026
·
Updated

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

5 affected componentsFixes available
Nginx NGINX Plus
Nginx NGINX Open Source
F5 NGINX Plus>=37.1.0<=37.2.0.1, >=37.0.0<=37.0.7.1
37.3.0.137.0.8.1
F5 NGINX Plus=34
F5 NGINX Open Source>=1.31.0<=1.31.8, >=1.25.0<=1.30.6
1.31.91.30.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 37.3.0.1Fixed in 37.0.8.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.31.9Fixed in 1.30.7

Event History

Nov 18, 2026
Advisory Published
via F5·02:49 PM
Data Sourced
via F5·02:49 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203