Tech9 min read

nginx HTTP/2 use-after-free and flow control bugs CVE-2026-123633 and CVE-2026-123007

IkesanContents

TL;DR

What’s affected nginx Open Source (1.9.5–1.31.8 for CVE-2026-123007; 1.19.7–1.31.8 for CVE-2026-123633) and commercial nginx Plus with HTTP/2 enabled. CVE-2026-123007 (flow control) hits any HTTP/2 config including static servers, while CVE-2026-123633 (use-after-free) triggers when proxying to backends and a worker reaches its worker_connections limit

What to do Upgrade nginx Open Source along your branch to 1.30.7 stable or 1.31.9 mainline. For nginx Plus, upgrade to 37.0.8.1+ on the 37.0 branch or 37.3.0.1+ on the 37.2–37.3 branches

Until then Disable HTTP/2 across every target server block:

  1. Set http2 off; (nginx 1.25.1+), strip http2 from all listen directives, and verify with nginx -T
  2. Run nginx -t and reload, noting graceful reload keeps existing HTTP/2 connections on old workers until closed
  3. Expect HTTP/2-only gRPC routes (grpc_pass) to break once traffic falls back to HTTP/1.1

On November 18, 2026, nginx.org released nginx 1.30.7 (the stable branch) and 1.31.9 (the mainline feature branch), patching 10 vulnerabilities in total.
Two of them sit in HTTP/2 handling: a use-after-free (CVE-2026-123633) and memory corruption in HTTP/2 flow control (CVE-2026-123007).

F5, acting as the CVE Numbering Authority (CNA), assigned both CVEs a CVSS v4.0 base score of 9.2 and CVSS v3.1 of 8.1 out of 10, while nginx.org’s own security advisory list classifies CVE-2026-123007 as major and CVE-2026-123633 as medium.
The CVSS vectors mark both as unauthenticated (PR:N) and reachable over the network (AV:N), with high attack complexity (AC:H), meaning an attacker can reach them remotely only when strict memory and configuration conditions line up. No public exploit code or active in-the-wild exploitation has been reported so far.

How the two vulnerabilities differ

Both bugs require HTTP/2 to be enabled in nginx, but they differ in affected versions, trigger conditions, and vendor severity ratings. Comparing the original advisories and CVE records gives the following breakdown.

ItemCVE-2026-123633CVE-2026-123007
nginx.org titleUse-after-free in HTTP/2Memory corruption in HTTP/2 flow control
Classification (CWE)CWE-416 Use After FreeCWE-191 Integer Underflow, CWE-787 Out-of-bounds Write
nginx.org severitymediummajor
CVSS v4.0 / v3.19.2 / 8.19.2 / 8.1
Affected Open Source versions1.19.7–1.31.81.9.5–1.31.8
Fixed Open Source versions1.30.7, 1.31.91.30.7, 1.31.9
Fixed nginx Plus versions37.0.7.1, 37.2.0.137.0.8.1, 37.3.0.1
Trigger conditionHTTP/2 proxy at worker_connections capAny HTTP/2 config
F5 advisoryK000163928K000163926

CVE-2026-123633 only triggers when nginx proxies incoming requests to backend application servers such as Node.js or PHP, so servers that only serve static files like HTML or images avoid this particular UAF bug. However, CVE-2026-123007 has no proxy requirement and applies to any nginx server with HTTP/2 enabled—static-only sites included—while front-end reverse proxies fall in scope for both CVEs.

Their underlying memory bugs are distinct. In CVE-2026-123633, the use-after-free occurs when code keeps using a memory region after releasing (freeing) it back to the OS; if attacker-controlled data fills that freed slot, subsequent execution reads corrupted state and can be hijacked.
In CVE-2026-123007, an unsigned integer underflow happens when subtraction drops below zero—instead of becoming -1, an unsigned integer wraps around to a huge positive number, which then serves as a copy length and causes an out-of-bounds write past the allocated buffer.

HTTP/2 flow control manages how many bytes a sender may transmit by having the receiver advertise a “window” of allowed bytes. According to the CVE-2026-123007 record, undisclosed crafted traffic pushes this window past its limit, triggering a heap-based buffer overflow that writes past dynamic heap memory and crashes the worker process with a segmentation fault. nginx’s CHANGES entry similarly calls it “a flow control window overflow in HTTP/2.”

How far exploitation can go

Per F5’s CVE records, the baseline impact for both flaws is denial of service (DoS) via worker process crashes, which can temporarily disrupt traffic. If ASLR (Address Space Layout Randomization, the OS defense that randomizes memory addresses) is disabled or an attacker can bypass it—by leaking addresses and shaping heap layout—both bugs can reach remote code execution (RCE). Both sit on the data plane that handles client traffic and do not expose the control plane.

nginx’s HTTP/2 stack also saw a memory-exhaustion DoS back in June using HPACK header compression and flow control (HTTP/2 Bomb: 5,700x Envoy, 4,000x Apache amplification via HPACK + flow control). Unlike that earlier flaw—which pinned memory until the server ran out—these two corrupt memory bounds and can lead to code execution, and Wiz Research confirmed an RCE path for CVE-2026-123007.

Wiz Research’s writeup

Wiz Research, one of the discovering teams, published a technical analysis on November 18, 2026 (Wiz Research). Five teams—Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint—found the two vulnerabilities independently, matching F5’s acknowledgements: Albert Ebb of Metnir, Nir Ohfeld of Wiz, and Xint.io for CVE-2026-123633; and Stephen Fewer of Rapid7, Tomer Schwartz of Wiz, Xint.io, and Ikotas Labs for CVE-2026-123007. nginx’s CHANGES file credits one party each—“Albert of Vexera AI” for CVE-2026-123633 and Xint.io for CVE-2026-123007—and Wiz notes that F5 confirmed another team had reported CVE-2026-123633 earlier.

On the root cause, Wiz explains that CVE-2026-123633 leaves an HTTP/2 connection in nginx’s list of reusable (idle) connections even after a request starts. Each nginx worker process caps simultaneous connections at worker_connections, so hitting that cap forces nginx to close entries from the reusable list to make room—freeing memory that the in-flight request still references. This matches the CHANGES note: “use-after-free might occur in a worker process when using HTTP/2 if worker_connections were not enough.”

CVE-2026-123007 stems from a flow-control accounting error where a client sends a flood of WINDOW_UPDATE frames (notices allowing the peer to send more bytes), pushing nginx’s internal send_window counter—which tracks how many bytes nginx may still transmit—past its maximum limit. When nginx next subtracts against that corrupted limit to bound a copy operation, the subtraction underflows into a massive number and causes an invalid memory copy past buffer bounds.
Using this mechanism, Wiz demonstrated code execution against an nginx instance serving plain static files over HTTPS without any backend app or third-party modules. While the underlying bug affects HTTP/2 configurations in general, Wiz’s working proof-of-concept (PoC) targeted a specific setup: 64-bit HTTP/2 over TLS returning response data from memory while the attacker sends large numbers of WINDOW_UPDATE frames.

Publicly documented reproduction details differ between the two bugs. Wiz states it achieved ASLR-bypassing RCE for CVE-2026-123007 on official nginx 1.31.7 and 1.31.8 builds, whereas for CVE-2026-123633 it only mentions verifying ASLR-bypassing RCE at report time without specifying the build or config tested.
In both cases, Wiz notes that remote exploitation remains hard because an attacker must leak memory addresses, shape heap layout, and handle version, build, and configuration differences. By contrast, a secondary writeup on The CyberSec Guru describes “reliable remote code execution,” wording that does not appear in Wiz’s post, and its footer links reference mismatched IDs (CVE-2026-127336 and CVE-2026-12307) that differ from its own headline.

Wiz is withholding exploit code and reports no known active exploitation. For triage, it suggests checking logs for unexpected worker crashes or child commands spawned by nginx, while cautioning that these are generic indicators rather than proof unique to these CVEs.

Remediation

To patch nginx Open Source, upgrade within your existing release branch to 1.30.7 stable or 1.31.9 mainline.
For commercial nginx Plus, patches split by branch: CVE-2026-123633 alone is fixed in 37.0.7.1 and 37.2.0.1, whereas fixing both including CVE-2026-123007 requires 37.0.8.1+ on the 37.0 line or 37.3.0.1+ on the 37.2–37.3 lines.
F5’s advisory tables list “None” under affected versions for older nginx Plus branches R34–R36, but both F5 and the CVE records note that versions past End of Technical Support are not evaluated—so older or unsupported releases are untested rather than confirmed safe.

Release 1.31.9 also fixes other bugs outside HTTP/2, including an HTTP/3 use-after-free (CVE-2026-121810), a resolver use-after-free (CVE-2026-123634), and a buffer overflow with try_files and alias (CVE-2026-125283). Setups with HTTP/2 disabled are not hit by these two HTTP/2 CVEs, yet they still benefit from upgrading for those parallel fixes.

Workarounds until you can upgrade

F5 lists official Mitigation as “None” for both CVEs—meaning there is no safe configuration tweak that leaves HTTP/2 active—so disabling HTTP/2 below is the interim workaround Wiz suggests until you can patch. Because both flaws require HTTP/2 to be active, turning it off removes the trigger path.

The exact config change depends on your nginx version.
On nginx 1.25.1 and later, the http2 directive toggles HTTP/2 per server block (the per-site or listener unit) and defaults to off; add http2 off; inside each server block to override any http2 on; inherited from an outer http block or include file, and also strip http2 from every listen line since listen ... http2 keeps it active even if http2 off; is missing or overridden elsewhere.
On versions older than 1.25.1, the http2 directive does not exist, so remove the http2 parameter from listen 443 ssl http2;.

server {
    listen 443 ssl;   # omit the http2 parameter on listen
    http2 off;

    ssl_certificate     server.crt;
    ssl_certificate_key server.key;
}

When configuration is split across files, run nginx -T to dump the full expanded config and locate every enabled site, then verify syntax with nginx -t before reloading.
Because nginx reloads gracefully, old worker processes remain alive until in-flight connections finish and keep serving existing HTTP/2 sessions under the prior config, so the workaround may not take effect immediately for every open connection; setting worker_shutdown_timeout caps how long those old workers can linger.

Once HTTP/2 is off, clients fall back to HTTP/1.1, which breaks HTTP/2-dependent protocols like gRPC (grpc_pass). Re-enable HTTP/2 after upgrading to a patched release.