CVE-2026-123633 is a use-after-free (CWE-416) in NGINX's HTTP/2 module (ngx_http_v2_module) affecting OSS >= 1.19.7 / NGINX Plus R33, fixed in OSS 1.30.7 (stable) / 1.31.9 (mainline). The official fix is the commit "HTTP/2: reset reusable connection status on stream creation" (1.31.9: 2df48a501d0fb8212b7d39dffeeff5876332ba59; 1.30.7: 0c87dd1db413e440a4e3ef7ee8acc518509e8809), which touches a single file, src/http/v2/ngx_http_v2.c, and a single function, ngx_http_v2_create_stream().\n\nRoot cause: NGINX keeps a list of "reusable" connections it may close when the worker runs low on free connection slots (ngx_drain_connections()). An HTTP/2 connection is registered as reusable by ngx_http_v2_handle_connection() when it has no active streams and has read only a partial frame (a DoS-avoidance behavior introduced in 76672e650). This is exactly what happens when an attacker sends only the first byte of a HEADERS frame. When the rest of the HEADERS frame later arrives, ngx_http_v2_create_stream() creates the request stream and increments h2c->processing, but (in the vulnerable build) never resets the reusable flag. The connection is therefore still on the reusable list while it owns an active stream. Forwarding that request to an upstream calls ngx_get_connection(); if free connection slots are low, ngx_drain_connections() can select this same connection. NGINX then attempts to send a GOAWAY frame; if creating/sending the GOAWAY fails (e.g. no reusable frame buffer available), the error path immediately closes the connection and frees its pool, while the original request code keeps dereferencing the now-freed connection/stream memory — a use-after-free that can lead to DoS and, with heap grooming/ASLR bypass, remote code execution.\n\nThe fix simply adds ngx_reusable_connection(h2c->connection, 0) right after h2c->processing++, i.e. it makes the stream-creating function remove the connection from the reusable list as soon as it owns a stream. Therefore the vulnerable function — the one the patch modified and that lacked the check — is ngx_http_v2_create_stream(). For a C build, a profiler/stack trace reports the bare symbol name with no namespace/module prefix.