# CVE-2026-121810: NGINX ngx_http_v3_module vulnerability

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

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **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, UBUNTU-CVE-2026-121810

## 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 (Use After Free)

## Which versions are affected by CVE-2026-121810?

It affects 7 products.

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


Products: F5 Dos, F5 NGINX Gateway Fabric, F5 NGINX Ingress Controller, F5 NGINX Instance Manager, F5 NGINX Open Source, F5 NGINX Plus, F5 Waf.

CPE match criteria (CPE 2.3):

- `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:*:*:*`
- `cpe:2.3:a:f5:nginx_ingress_controller:3.7.2:*:*:*:continuous_releases:*:*:*`
- `cpe:2.3:a:f5:nginx_ingress_controller:4.0.0:*:*:*:continuous_releases:*:*:*`
- `cpe:2.3:a:f5:nginx_ingress_controller:4.0.1:*:*:*:continuous_releases:*:*:*`
- `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:*:*:*:*:*:*:*`
- `cpe:2.3:a:f5:nginx_plus:r35:*:*:*:*:*:*:*`
- `cpe:2.3:a:f5:nginx_plus: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

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `f5:dos`, `f5:nginx_gateway_fabric`, `f5:nginx_ingress_controller` and 4 more | 4.13.0, 2.9.0, 2026-lts-r11 |

## How do I fix CVE-2026-121810?

Apply the vendor's patch.

## 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:

- CVE-2026-121810 — nginx HTTP/3 (QUIC) use-after-free under worker_connections exhaustion. Affects nginx 1.25.0–1.31.8. Docker PoC. (github_poc): https://github.com/LLCForge/CVE-2026-121810

## Other vulnerabilities in F5 NGINX Open Source

- [CVE-2026-113425](https://insights.sbomify.com/CVE-2026-113425/): NGINX ngx_mail_proxy_module vulnerability (critical 9.2)
- [CVE-2026-123007](https://insights.sbomify.com/CVE-2026-123007/): NGINX ngx_http_v2_module vulnerability (critical 9.2)
- [CVE-2026-123633](https://insights.sbomify.com/CVE-2026-123633/): NGINX ngx_http_v2_module vulnerability (critical 9.2)
- [CVE-2026-123634](https://insights.sbomify.com/CVE-2026-123634/): NGINX resolver vulnerability (critical 9.2)
- [CVE-2026-15176](https://insights.sbomify.com/CVE-2026-15176/): NGINX ngx_http_core_module vulnerability (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121810 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-121810 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: F5 NGINX Open Source. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121810/ (Markdown: https://insights.sbomify.com/CVE-2026-121810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121810
- OSV: https://osv.dev/vulnerability/CVE-2026-121810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121810/
Summaries are generated and may contain mistakes; the official description above is the record.
