Update — November 19: Researchers demonstrate code execution
Wiz’s technical disclosure confirms laboratory code execution through both HTTP/2 flaws, CVE-2026-123633 and CVE-2026-123007, including an ASLR bypass. The latter can affect an HTTP/2-enabled NGINX server serving ordinary static files; a vulnerable application behind NGINX is not required. Both have configuration and exploitation constraints, and public researcher demonstrations are not confirmation of widespread malicious exploitation.
Rapid7’s independent demonstration of CVE-2026-123007 required roughly 128 GB of HTTP/2 data in a tested Linux/x86-64 build, illustrating that network and CPU conditions affect practical exploitation. The supported remediations remain NGINX Open Source 1.30.7 stable or 1.31.9 mainline and the applicable NGINX Plus engineering releases. Administrators should prioritize exposed HTTP/2 endpoints and not confuse a lab demonstration with evidence of a compromised host.
NGINX administrators have a new security update to assess after November 18 disclosures concerning remote code execution. CERT-EU says researchers demonstrated CVE-2026-123007, but reports no exploitation in the wild. Successful exploitation would run with the privileges of the NGINX worker process.
The upstream advisory list identifies CVE-2026-123007 as HTTP/2 flow-control memory corruption affecting versions 1.9.5–1.31.8. NGINX 1.31.9 and 1.30.7, or later releases in those branches, address it.
The same fixed releases address HTTP/2 use-after-free CVE-2026-123633, HTTP/3 use-after-free CVE-2026-121810, resolver-response CVE-2026-123634 and mail-proxy CVE-2026-113425. Their affected ranges differ, so a version match should be checked against the relevant entry rather than treating every module as equally exposed.
Updates depend on edition and branch
The NGINX Plus release notes list PLS.37.0.8.1 LTS and PLS.37.3.0.1 CR security releases dated November 18. Plus customers should follow their own supported release track. The LTS notes show CVE-2026-123633 was already fixed in PLS.37.0.7.1 on October 14; the newly disclosed issues do not all share the same first fixed Plus build.
CERT-EU says the HTTP/2 flow-control issue requires HTTP/2 on a listening port. Disabling HTTP/2 can mitigate CVE-2026-123007 and CVE-2026-123633 while an upgrade is arranged, but that measure does not address the other disclosed flaws.
IPCRIME analysis: check the running service
Build the deployment list around actual traffic paths. Include public reverse proxies, internal gateways and mail services, then identify which package or appliance supplies each NGINX process. A container rebuild, a distribution package update and a commercial appliance upgrade may require different owners and different maintenance procedures.
After applying the applicable update, verify the executable and worker processes that are serving traffic. Retest upstream connectivity, authentication and representative large requests before closing the change. Record any temporary protocol restriction so it can be reviewed once a fixed release is in service.
Treat unexpected worker crashes as a reason to inspect logs and preserve evidence, rather than as proof of successful code execution. The operational goal is to establish which instances were affected, whether their configuration exposed the relevant feature, and whether the verified fix is now running.
Related reading: SSLyze: Automated TLS security configuration review — Digital Arsenal.
Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.
