1-minute read of a 4 min report

Two NGINX HTTP/2 Flaws Expose Web Servers to Code Execution

By

1-minute read

What a defender needs to know

Two HTTP/2 memory flaws in NGINX can let an unauthenticated attacker execute code in a traffic-handling worker. CVE-2026-123633 involves a connection kept on the reusable list while a reverse-proxied request is active and the worker runs low on connection slots. CVE-2026-123007 involves faulty flow-control accounting; Wiz demonstrated code execution on a 64-bit HTTPS server serving static files, with no application backend. Both require HTTP/2. F5’s CVE records describe code execution when ASLR is disabled or bypassed; Wiz reports a demonstrated bypass.

Find NGINX Open Source and Plus listeners that accept HTTP/2. OSS 1.30.7 stable and 1.31.9 mainline fix both issues. Plus has different fix rows for each CVE: 37.0.7.1 or 37.2.0.1 for the first; 37.0.8.1 or 37.3.0.1 for the second. Match the running build against both fixes for its release line. If upgrading must wait, Wiz recommends disabling HTTP/2 in affected server blocks, testing compatibility, reloading, and waiting for old workers to exit. On 1.25.1 or later, set http2 off; and remove http2 from listen directives.

Verify the running worker build and HTTP/2 negotiation on each affected listener. Investigate unexpected worker crashes or NGINX-launched child processes in service and process logs as general warning signs, alongside host activity; they are not exploit-specific indicators.

Primary sources