# CVE-2026-123633: NGINX ngx_http_v2_module vulnerability

> Remote attackers can send crafted HTTP/2 requests to trigger a use-after-free in NGINX worker processes, crashing them or executing code.

- **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-123633, AZL-114598, BELL-CVE-2026-123633, DEBIAN-CVE-2026-123633, DHI-47k2-tpb3-2uyg-5xmp, ECHO-5a26-51a7-3011, GHSA-7xxj-p8w5-434q, UBUNTU-CVE-2026-123633

## What is CVE-2026-123633?

CVE-2026-123633 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

When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. 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 may allow 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-123633?

It affects 10 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, Red Hat 3scale API Management Platform, Red Hat Enterprise Linux, Red Hat Hardened Images.

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.24.0
- `cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:*` from 1.19.7 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.7.1
- `cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:*` from 37.1.0 before 37.2.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
- `cpe:2.3:a:redhat:3scale_api_management_platform:2.0:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:enterprise_linux:10.0:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:hardened_images:-:*:*:*:*:*:*:*`

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-123633?

Upgrade to a fixed version.

## Is CVE-2026-123633 being exploited?

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

Public exploit code:

- Exploits e PoCs para vulnerabilidades no NGINX - CVE-2026-123633, CVE-2026-123007 (github_poc): https://github.com/Ghost-Bx1/nginx-exploits
- CVE-2026-123633 — nginx HTTP/2 use-after-free under connection exhaustion (RST_STREAM race). CVSS 8.1. Affects nginx 1.19.7–1.31.8. Docker PoC. (github_poc): https://github.com/LLCForge/CVE-2026-123633
- Read-only POSIX sh audit for the five NGINX2Root nginx CVEs (HTTP/2, HTTP/3, resolver, mail proxy), judged per CVE (github_poc): https://github.com/Quaerendir/cve-2026-123633-123007-nginx-audit
- Exploits e PoCs para vulnerabilidades no NGINX - CVE-2026-123633, CVE-2026-123007 (github_poc): https://github.com/0xsaju/nginx-exploits

## 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-121810](https://insights.sbomify.com/CVE-2026-121810/): NGINX ngx_http_v3_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-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-123633 and fix it if it is affected.

What it is: CVE-2026-123633 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-123633 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-123633/ (Markdown: https://insights.sbomify.com/CVE-2026-123633/index.md)
```

## Sources

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

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