F5 says malformed traffic can drive a window past its allowed limit, leading to a heap buffer overflow and usually a worker crash.F5 says remote code execution is possible if ASLR is disabled or bypassed. Wiz Research reports an ASLR bypass and code execution in its laboratory tests on official 1.31.7 and 1.31.8 builds. Those tests do not establish exploitation in the wild.
What it allows
How Does CVE-2026-123007 Reach NGINX Memory?
Wiz Research describes an accounting error in the HTTP/2 connection send window. When unsent response data is discarded, NGINX refunds its flow control credit without enforcing the protocol maximum. A later unsigned subtraction can then underflow, so a bounds check accepts an invalid window value.
Wiz says a later signed conversion can turn that invalid value into a negative response length. The malformed buffer can reach an out-of-bounds memory copy in the TLS send path. F5 describes the outcome as memory corruption, commonly a worker segmentation fault, with potential remote code execution under its ASLR conditions.
Wiz reports laboratory code execution with an ASLR bypass on 64-bit servers using HTTP/2 over TLS. It demonstrated the path while NGINX served ordinary static files, without a backend application or third-party module. The researchers' tested result is narrower than a claim that every affected deployment is exploitable.
Our defensive reading is to treat unexplained worker crashes as an investigation lead and correlate them with HTTP/2 traffic. Wiz also suggests looking for unusual long-lived HTTP/2 connections with heavy data exchange. Neither observation alone identifies this CVE.
Brandefense Blackhole counted two dark chat posts matching CVE-2026-123007 from August 20 through November 18, 2026. The measured unit is posts, not attacks; those conversations do not establish active exploitation.
The dispatcher’s GitHub repository search returned one public repository named for CVE-2026-123007 on November 18, 2026. Its description claims proof-of-concept scripts; this is a repository count and an author claim, not a verified exploit or incident.
Who is affected
Which CVE-2026-123007 NGINX Versions Need Action?
F5 lists NGINX Open Source with ngx_http_v2_module from 1.9.5 and affected 1.30 and 1.31 branches. Wiz identifies 1.30.7 stable and 1.31.9 mainline as fixed releases. Check the actual running binary and whether HTTP/2 is enabled on each internet-facing or internal listener.
F5 also lists NGINX Plus R33 and two affected 37.x ranges: 37.0.0 to before 37.0.8.1, and 37.1.0 to before 37.3.0.1. Wiz reports the same two fixed builds. The F5 record does not supply a comparable fixed build for R33, so verify a supported upgrade path with F5.
HTTP/2 must be enabled for this flaw to apply. F5 calls it a data plane issue without control plane exposure. Unlike CVE-2026-123633, this flaw does not require NGINX to proxy an upstream request or run low on free connection slots.
For a related planning method, see our vulnerability alert triage guide. The vulnerability intelligence definition explains how context changes priority. Teams managing many deployments can assess exposure through the vulnerability intelligence platform.
Timeline
-
2026-11-16
Wiz Research says it reported the HTTP/2 window flaw to F5.
-
2026-11-17
Wiz Research says F5 matched its report to CVE-2026-123007.
-
2026-11-18
F5 published the CVE record and coordinated disclosure.
What to do
-
Inventory HTTP/2 NGINX deployments
Identify NGINX Open Source and Plus instances serving HTTP/2, including direct content servers. Record the running binary version, enabled module and listener configuration, then prioritize reachable affected instances.
-
Install a fixed release
Upgrade NGINX Open Source to 1.30.7 stable or 1.31.9 mainline. For NGINX Plus, use the appropriate F5 fixed build, 37.0.8.1 or 37.3.0.1, and confirm the supported path for R33.
-
Verify the running version after maintenance
Confirm that each service actually runs the intended fixed binary after reload or restart. Recheck the HTTP/2 listener and package build, especially when a distribution backports security fixes.
-
Temporarily remove HTTP/2 exposure if needed
Wiz recommends disabling HTTP/2 when an upgrade cannot be completed promptly. Test compatibility, reload NGINX and confirm old workers have exited; restore HTTP/2 after the fixed build is running.
-
Investigate suspicious worker behavior
Review unexpected worker crashes and commands launched by NGINX as general warning signs. Correlate with unusual HTTP/2 connection behavior; neither signal proves exploitation of this flaw.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-123007 in Brandefense Atlas
The Atlas record of CVE-2026-123007: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-123007 require authentication?
No authentication is required in the F5 CVSS vectors. The affected NGINX server must process HTTP/2 traffic; F5 conditions code execution on ASLR being disabled or bypassed.
Can a server serving only static files be affected?
Yes. Wiz Research reports laboratory code execution against NGINX serving ordinary static files over HTTP/2 and TLS, without a backend application or third-party module.
Which releases fix CVE-2026-123007?
Wiz lists NGINX Open Source 1.30.7 stable and 1.31.9 mainline. F5's CVE record gives NGINX Plus fixed boundaries of 37.0.8.1 and 37.3.0.1.
Is CVE-2026-123007 the same as CVE-2026-123633?
No. CVE-2026-123007 concerns an HTTP/2 send-window underflow and can affect direct content serving. CVE-2026-123633 is a separate use-after-free with proxy and connection-pressure conditions.