Skip to main content
Menu
CVEs

CVE

F5 NGINX Open Source memory corruption in HTTP/2 module

Affects NGINX Open Source 1.19.7 to 1.31.8 and NGINX Plus when HTTP/2 is configured as a proxy server. Listed fixes: 1.30.7 and 1.31.9 for Open Source, 37.0.7.1 and 37.2.0.1 for Plus.

CVE-2026-123633EUVD-2026-128944GHSA-7XXJ-P8W5-434QPublished Updated Summary written by a modelNeeds attention

8.1HighCNA
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.0.1, 37.0.7.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.0.1, 37.0.7.1.

Summary

NGINX Open Source and NGINX Plus are affected when configured to use HTTP/2 for client connections and proxy those requests to a backend. Remote attackers can reach the flaw over the network without logging in, using a specially crafted request that can crash the worker process or, on systems with ASLR disabled or bypassed, allow code execution.

Original 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.

Who should check

Teams running NGINX OSS 1.19.7-1.31.8 or NGINX Plus with HTTP/2 enabled as a reverse proxy to backends, including nginx-based front doors

“CVE-2026-123633 UAF in HTTP/2 Exploitable configured with HTTP/2 as a proxy server 9.2 1.19.7-1.31.8”

wiz.io

cve.now Index

65Pcve.now Index 65 of 100 · methodology v3 · provisional
  • Exploitation22/40Public exploit on Exploit-DB or GitHub
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach17/20Affects nginx (a widely deployed server, runtime, framework or database)
  • Severity9.1/10CVSS 8.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 88 if added to CISA KEV
  • Would score about 83 if CISA's SSVC rates exploitation active
  • Would score about 70 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.0.1, 37.0.7.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-123633 (NGINX ngx_http_v2_module vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123633 (entry last updated 2026-11-18):
Affected:
- F5 NGINX Open Source: from 1.31.0, fixed in 1.31.9; from 1.30.0, fixed in 1.30.7; from 1.19.7
- F5 NGINX Plus: from 37.1.0.1, fixed in 37.2.0.1; from 37.0.0.1, fixed in 37.0.7.1; from R33
Fixed versions: 1.31.9, 1.30.7, 37.2.0.1, 37.0.7.1.
Conditions (all must be true for the bug to be hit):
- HTTP/2 is enabled on the NGINX server (source: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
- NGINX is used as a reverse proxy and available connection slots run low (source: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
- Affected NGINX versions 1.19.7 through 1.31.8 with HTTP/2 configured as a proxy server (source: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-123633 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123633 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.f5.com/manage/s/article/K000163928
- https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
- https://news.ycombinator.com/item?id=50547374
- https://github.com/nginx/nginx/commit/0c87dd1db413e440a4e3ef7ee8acc518509e8809
- https://ubuntu.com/security/CVE-2026-123633
- https://github.com/advisories/GHSA-7xxj-p8w5-434q
- https://github.com/openresty/openresty/issues/1165
- https://github.com/nginx/nginx/issues/2002
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123633
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123633"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. cve.now early warning

    F5 discloses NGINX HTTP/2 flaw CVE-2026-123007 that can allow code execution

  4. Posted on X by cve.now
  5. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  6. Exploit code on GitHub

    Ghost-Bx1/nginx-exploits, LLCForge/CVE-2026-123633

  7. Record last updated

Affected versions

  • F5 NGINX Open Source

    From 1.31.0 · fixed in 1.31.9; From 1.30.0 · fixed in 1.30.7; From 1.19.7

  • F5 NGINX Plus

    From 37.1.0.1 · fixed in 37.2.0.1; From 37.0.0.1 · fixed in 37.0.7.1; From R33

Evidence 16

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123633

Is CVE-2026-123633 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data

What does this mean?

This is a use-after-free bug in the NGINX HTTP/2 module. The checked facts say an unauthenticated attacker could execute arbitrary code on the NGINX server, and that the issue affects reverse-proxy processing when available connection slots run low.Source: wiz.io

Which versions are affected by CVE-2026-123633?

NGINX Open Source: from 1.31.0 before 1.31.9; from 1.30.0 before 1.30.7; from 1.19.7. NGINX Plus: from 37.1.0.1 before 37.2.0.1; from 37.0.0.1 before 37.0.7.1; from R33.Source: cve.now feed data

Am I affected, and how do I check?

The checked facts list NGINX Open Source versions 1.19.7 through 1.31.8 configured with HTTP/2 as a proxy server, and NGINX Plus from R33 onward in the listed ranges. HTTP/2 must be enabled on the server. To check, run nginx -v for the version and search the configuration for the http2 parameter on listen directives.Source: wiz.io

How do I fix CVE-2026-123633?

The product data lists fixed versions 1.30.7 and 1.31.9 for NGINX Open Source, and 37.0.7.1 and 37.2.0.1 for NGINX Plus. The checked facts do not state a fix for the 1.19.x branch, so confirm the target with F5's advisory before upgrading.Source: wiz.io

More CVEs