Two newly disclosed flaws in NGINX’s HTTP/2 handling can let an unauthenticated attacker run code on a web server. The server at risk may be the shared front door for several websites and APIs. Wiz Research demonstrated code execution for both CVE-2026-123633 and CVE-2026-123007; F5 released fixes on November 18. Both issues require HTTP/2 on the NGINX instance, but one also depends on proxying and scarce worker connections. The other reached a server serving static files in Wiz’s test.

Wiz estimates that NGINX powers more than 225 million websites; that figure describes sites using NGINX, not affected deployments. Wiz writes: “Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.” Wiz reproduced the static-file path over TLS on 64-bit systems running official 1.31.7 and 1.31.8 builds. Check internet-facing and internally reachable HTTP/2 endpoints, including servers that serve only files.

Two bugs, different exposed paths

CVE-2026-123633 is a use-after-free in an HTTP/2 worker processing requests through a reverse proxy. An active connection can remain on NGINX’s reusable-connection list. If the worker runs low on available worker_connections while opening an upstream connection, it can close the connection its own request still uses. F5’s CVE record identifies the low-connection and backend-proxy conditions; it describes denial of service or code execution when ASLR is disabled or bypassed. Wiz says it demonstrated an ASLR bypass. This affects the traffic-handling worker, not an administrative interface.

CVE-2026-123007 involves HTTP/2 flow-control accounting. The window can exceed its allowed threshold, leading to an invalid memory operation and possible worker crash or code execution. F5’s record describes a heap buffer overflow and the same ASLR condition for code execution; Wiz describes the underlying integer underflow and reports code execution over HTTPS on a 64-bit server serving static files. That means a proxy-only inventory misses a demonstrated path.

F5 assigns each issue a 9.2 CVSS 4.0 score in its CVE records. NGINX’s own advisory list labels the flow-control issue “major” and the use-after-free “medium.” The labels use different rating systems; the operational test is whether the deployed build and HTTP/2 configuration match an affected path. The two fixes ship together in current NGINX Open Source releases, while NGINX Plus has separate fix rows.

Match both fixes to deployed builds

Affected NGINX Open Source versions start at 1.19.7 for CVE-2026-123633 and 1.9.5 for CVE-2026-123007, before the fixed release on each supported branch and when the relevant HTTP/2 conditions apply. NGINX lists 1.30.7 stable and 1.31.9 mainline as releases free of both issues. Compare the running build, including packaged or containerized copies, with the vendor’s affected-version list; check that distributor’s advisory for backports. F5 classifies end-of-technical-support releases as unevaluated; check older unsupported builds separately.

For NGINX Plus, Wiz lists 37.0.7.1 and 37.2.0.1 as fixes for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007; affected versions reach back to R33. The 37.0.7.1 row addresses one flaw, so choose a Plus build that addresses both for the installed release line. Consult F5’s corresponding advisory before the change.

Turn off HTTP/2 during rollout

If a fix must wait, Wiz recommends temporarily disabling HTTP/2 on affected server blocks. On NGINX 1.25.1 or later, set http2 off; and remove the http2 parameter from listen directives. Test clients and application compatibility, reload NGINX, and confirm the old workers have exited. Re-enable HTTP/2 after the corrected build is running. F5’s CVE entries list no formal workaround; this interim change removes the protocol prerequisite Wiz identifies for these two paths.

Verify the edge actually changed

Inventory the NGINX instances accepting HTTP/2, including static-file servers and shared reverse proxies. Record the deployed OSS or Plus build and the effective HTTP/2 state for each listener, then upgrade to a build that covers both CVEs or disable the protocol during rollout. After reload or replacement, verify the running workers use the intended build, old workers have exited, and an external protocol check on each affected listener matches the intended HTTP/2 state. A package-install record alone misses stale processes and unchanged containers.

Investigate unexplained NGINX worker crashes in process and service logs, and unexpected child processes launched by NGINX workers. Wiz calls those general warning signs, not signatures of either vulnerability; correlate them with listener exposure and host activity before assigning a cause.