CVE-2026-121810 NGINX ngx_http_v3_module vulnerability

Critical 9.2 Published Updated

Unauthenticated remote attackers can trigger a use-after-free in NGINX HTTP/3 handling, crashing workers or possibly executing code; NGINX operators should patch.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Harmful if only installed
No
Needs a specific call
No
Fix
Available

What is CVE-2026-121810?

CVE-2026-121810 is a critical use after free vulnerability in F5 NGINX Open Source, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-416

Which versions are affected by CVE-2026-121810?

It affects 7 products.

Only installations with a non-default setting turned on are exposed.

Status by vendor (1)
WhoReleaseStatusPackages
Upstreamfixedf5:dos (4.13.0), f5:nginx_gateway_fabric (2.9.0), f5:nginx_ingress_controller (2026-lts-r11) and 4 more

Products include F5 Dos, F5 NGINX Gateway Fabric, F5 NGINX Ingress Controller, F5 NGINX Instance Manager, F5 NGINX Open Source, F5 NGINX Plus and 1 more.

CPE match criteria (21)
CPE 2.3Versions
cpe:2.3:a:f5:dos:*:*:*:*:*:nginx:*:*from 4.5.0, up to 4.7.0
cpe:2.3:a:f5:dos:*:*:*:*:*:nginx:*:*from 4.8.0, before 4.13.0
cpe:2.3:a:f5:nginx_gateway_fabric:*:*:*:*:*:*:*:*from 1.5.0, up to 1.6.2
cpe:2.3:a:f5:nginx_gateway_fabric:*:*:*:*:*:*:*:*from 2.0.0, before 2.9.0
cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:continuous_releases:*:*:*from 5.0.0, before 5.8.0
cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:long-term_support:*:*:*from 2026-lts-r1, before 2026-lts-r11
cpe:2.3:a:f5:nginx_ingress_controller:3.7.1:*:*:*:continuous_releases:*:*:*3.7.1
cpe:2.3:a:f5:nginx_ingress_controller:3.7.2:*:*:*:continuous_releases:*:*:*3.7.2
cpe:2.3:a:f5:nginx_ingress_controller:4.0.0:*:*:*:continuous_releases:*:*:*4.0.0
cpe:2.3:a:f5:nginx_ingress_controller:4.0.1:*:*:*:continuous_releases:*:*:*4.0.1
cpe:2.3:a:f5:nginx_instance_manager:*:*:*:*:*:*:*:*from 2.18.0, before 2.25.0
cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:*from 1.25.0, before 1.30.7
cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:*from 1.31.0, before 1.31.9
cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:*from 37.0.0, before 37.0.8.1
cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:*from 37.1.0, before 37.3.0.1
cpe:2.3:a:f5:nginx_plus:r34:*:*:*:*:*:*:*r34
cpe:2.3:a:f5:nginx_plus:r35:*:*:*:*:*:*:*r35
cpe:2.3:a:f5:nginx_plus:r36:*:*:*:*:*:*:*r36
cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:*from 4.12.0, up to 4.16.0
cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:*from 5.4.0, up to 5.8.0
cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:*from 5.9.0, before 5.16.2

How do I fix CVE-2026-121810?

Apply the vendor's patch.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2026-121810 being exploited?

There is no known exploitation of CVE-2026-121810 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

All F5 NGINX Open Source vulnerabilities

Sources

Also known as ALPINE-CVE-2026-121810, BELL-CVE-2026-121810, DEBIAN-CVE-2026-121810, DHI-7tld-lwyf-txnr-62cl, ECHO-ed13-291e-ca3f, GHSA-fxx2-rrmx-x4v2 and 1 more.

Is CVE-2026-121810 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free