CVE-2026-123633

NGINX ngx_http_v2_module vulnerability

Published Nov 18, 2026 CVSS 4.0 · 9.2 Critical EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

NGINX Plus and the open‑source edition suffer a use‑after‑free bug when HTTP/2 client connections are proxied to a backend and the worker process is low on worker_connections. A crafted request can trigger a memory corruption event that, if the system has Address Space Layout Randomization disabled or the attacker can bypass it, may lead to arbitrary code execution. In environments where ASLR and other mitigations are active, the same flaw still enables attackers to terminate the process, resulting in a denial‑of‑service attack against the NGINX data plane.

Affected Systems

The vulnerability affects F5’s NGINX Open Source and NGINX Plus products. No specific patched or vulnerable release numbers are provided in the data, so all deployments of these products that have not been updated beyond the current branch may be susceptible.

Risk and Exploitability

The flaw carries a CVSS score of 9.2, indicating high severity. EPSS data is unavailable, and the issue is not listed in CISA’s KEV catalog. The most likely attack vector is remote exploitation over the network through a malformed HTTP/2 request. An attacker can achieve a denial of service by crashing the worker process, and if mitigations such as ASLR are bypassed, remote code execution becomes possible.

Remediation

Vendor Workaround

None


OpenCVE Recommended Actions

  • Update NGINX to the latest patched release as identified by the referenced commit on the official repository
  • If an immediate patch cannot be applied, disable HTTP/2 for client connections or increase worker_connections to mitigate use‑after‑free conditions
  • Ensure that Address Space Layout Randomization and other memory‑sanitization features are enabled to reduce the risk of code execution when a crash occurs

Generated by OpenCVE AI on November 19, 2026 at 02:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared F5
F5 nginx Open Source
F5 nginx Plus
Vendors & Products F5
F5 nginx Open Source
F5 nginx Plus
Type Values Removed Values Added
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.
Title NGINX ngx_http_v2_module vulnerability
Weaknesses CWE-416
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.2, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
f5
Published
Updated
Nov 18, 2026, 10:17 PM
Reserved
Nov 9, 2026, 6:42 PM
Status
Received
Published
Nov 18, 2026, 4:18 PM
Modified
Nov 18, 2026, 11:17 PM
Severity
Critical
Public date
Nov 18, 2026, 3:23 PM