CVE
F5 NGINX Plus memory corruption in HTTP/2 module via integer underflow
Affects NGINX Plus and NGINX Open Source with HTTP/2 enabled, including versions dating back to 1.9.5. Fixed in NGINX Plus 37.0.8.1 and 37.3.0.1, and in NGINX Open Source 1.30.7 and 1.31.9.
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.
Summary
F5's NGINX Plus and NGINX Open Source are affected when they use HTTP/2. A remote attacker who can reach the server without logging in can crash an NGINX worker process or corrupt its memory, and may be able to execute code, but only if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass it.
Original description
This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. 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.
cve.now Index
- 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 Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.
Workaround: Temporarily disable HTTP/2 (set http2 off; and remove the http2 parameter from listen directives) until upgraded.
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-123007 (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-123007 (entry last updated 2026-11-18):
Affected:
- F5 NGINX Plus: from 37.1.0, fixed in 37.3.0.1; from 37.0.0, fixed in 37.0.8.1; from R33
- F5 NGINX Open Source: from 1.31.0, fixed in 1.31.9; from 1.30.0, fixed in 1.30.7; from 1.9.5
Fixed versions: 37.3.0.1, 37.0.8.1, 1.31.9, 1.30.7.
Conditions (all must be true for the bug to be hit):
- HTTP/2 must be enabled on the NGINX server. (source: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
- Affects NGINX versions dating back to 1.9.5. (source: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
- Demonstrated by the researchers over HTTPS on 64-bit systems serving content directly. (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.
Workaround: Temporarily disable HTTP/2 (set http2 off; and remove the http2 parameter from listen directives) until upgraded. (source: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
CISA KEV: CVE-2026-123007 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123007 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/K000163926
- https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
- https://news.ycombinator.com/item?id=50547374
- https://github.com/nginx/nginx/commit/b89c4100bf6762a45e4a6463eaf4b70368277c94
- https://ubuntu.com/security/CVE-2026-123007
- https://github.com/advisories/GHSA-m4q8-cf44-f42r
- 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-123007
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-123007"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- cve.now early warning
F5 discloses NGINX HTTP/2 flaw CVE-2026-123007 that can allow code execution
- Record last updated
- Exploit code on GitHub
LLCForge/CVE-2026-123007, WormW/nginx2root-rce-lab, sfewer-r7/CVE-2026-123007
Affected versions
- F5 NGINX Plus
From 37.1.0 · fixed in 37.3.0.1; From 37.0.0 · fixed in 37.0.8.1; From R33
- F5 NGINX Open Source
From 1.31.0 · fixed in 1.31.9; From 1.30.0 · fixed in 1.30.7; From 1.9.5
Evidence 20
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123007
Is CVE-2026-123007 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?
The bug lets an attacker execute arbitrary code on the NGINX server without authentication.Source: wiz.io
Which versions are affected by CVE-2026-123007?
NGINX Plus: from 37.1.0 before 37.3.0.1; from 37.0.0 before 37.0.8.1; from R33. NGINX Open Source: from 1.31.0 before 1.31.9; from 1.30.0 before 1.30.7; from 1.9.5.Source: cve.now feed data
Am I affected, and how do I check?
Affected setups have HTTP/2 enabled on the NGINX server, and the bug dates back to NGINX 1.9.5. The researchers demonstrated it over HTTPS on 64-bit systems serving content directly. To check a server, run nginx -V for its version and review the configuration for http2 settings in listen directives.Source: wiz.io
How do I fix CVE-2026-123007?
Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), or upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1. Until the upgrade, temporarily disable HTTP/2 by setting http2 off; and removing the http2 parameter from listen directives.Source: wiz.io