Alert

Logo de NGINX

Alert 2026-170 Remote code execution in NGINX due to two HTTP/2 flaws

Affected product(s): 

ProductAffected versionsFix
NGINX Open Source (CVE-2026-123633)1.19.7 to 1.31.8 (on the stable branch, 1.30.0 to 1.30.6)1.30.7 (stable) or 1.31.9 (mainline)
NGINX Open Source (CVE-2026-123007)1.9.5 to 1.31.8 (on the stable branch, 1.30.0 to 1.30.6)1.30.7 (stable) or 1.31.9 (mainline)
NGINX Plus (CVE-2026-123633)From R33; on 37.x, versions earlier than 37.0.7.1 (LTS) and 37.2.0.1 (CR)37.0.7.1 LTS or 37.2.0.1 CR (Oct 14, 2026)
NGINX Plus (CVE-2026-123007)From R33; on 37.x, versions earlier than 37.0.8.1 (LTS) and 37.3.0.1 (CR)37.0.8.1 LTS or 37.3.0.1 CR (Nov 18, 2026)

Both flaws require HTTP/2 to be enabled. CVE-2026-123633 also occurs when NGINX proxies requests to a backend and the worker process is running low on worker_connections. The vendor’s official record names NGINX Open Source and NGINX Plus. In Open Source, the HTTP/2 module is not built by default. According to the vendor, installations without HTTP/2 enabled are not affected.

Description

Two vulnerabilities have been reported in NGINX’s HTTP/2 module that allow unauthenticated remote code execution. They are identified as CVE-2026-123633 and CVE-2026-123007. The vendor made them public on Nov 18, 2026 at 12:00 p.m. (PYT) and assigns them CVSS 9.2, critical; it also publishes CVSS 8.1, high. This bulletin is classified as CRITICAL. Both require HTTP/2 to be enabled.

CVE-2026-123633 is a use-after-free. According to the vendor, it occurs when NGINX uses HTTP/2 for client connections, proxies requests to a backend, and the worker process is running low on available connections (worker_connections). It can cause a denial of service or code execution. The vendor states that the latter path applies when ASLR is disabled or can be bypassed. It affects NGINX Open Source from 1.19.7 through 1.31.8 (on the stable branch, through 1.30.6) and NGINX Plus from R33, including the 37.x line earlier than 37.0.7.1 (LTS) and 37.2.0.1 (CR).

CVE-2026-123007 is a flaw in the HTTP/2 flow-control window: the window can exceed the allowed threshold and lead to a heap overflow, typically followed by a worker-process crash, or, potentially, allow remote code execution. It does not require a backend: HTTP/2 being in use is enough. The vendor also conditions code execution on ASLR being disabled or bypassable. An independent assessment demonstrated unauthenticated code execution, including with ASLR, on a server that only served static files. This flaw is present from NGINX 1.9.5 (2015) through 1.31.8 and 1.30.6, and in NGINX Plus from R33, including the 37.x line earlier than 37.0.8.1 (LTS) and 37.3.0.1 (CR).

On Nov 18, 2026, NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline) were published, fixing both flaws, together with NGINX Plus 37.0.8.1 LTS and 37.3.0.1 CR, which fix CVE-2026-123007. CVE-2026-123633 was already fixed in Plus 37.0.7.1 LTS and 37.2.0.1 CR, dated Oct 14, 2026; those versions remain exposed to CVE-2026-123007 until today’s update is applied. Open Source branches earlier than 1.30 and Plus branches R33 through R36 have no minor release in this batch: they must move to a fixed version (on Plus, to one of the 37.x releases indicated above).

The vendor does not report that these flaws have been used in real attacks. A public proof of concept has been published for CVE-2026-123007; no equivalent has been identified for CVE-2026-123633. These releases also fix other security flaws that are not the subject of this bulletin. As a protocol antecedent, not the same flaw, Alert 2026-162 covered remote code execution in HTTP/2 on Apache HTTP Server (mod_http2), a different product and a different CVE. Any product that embeds a vulnerable NGINX with HTTP/2 enabled could remain exposed until its vendor publishes its own update.

Mitigation

The confirmed fix is to update to the versions listed in Solution, starting with NGINX instances that have HTTP/2 enabled and are reachable from the internet. Also inventory NGINX Plus 37.0.7.1 and 37.2.0.1 installations, which already cover CVE-2026-123633 but not CVE-2026-123007, and branches R33 through R36, which must move to a fixed 37.x release. The inventory should also include images and products that embed NGINX.

The vendor does not publish a workaround. As a temporary measure until the patch is applied, HTTP/2 can be disabled: on 1.25.1 or later, with http2 off; in the affected server blocks, and, in earlier configurations, by removing the http2 parameter from listen directives. Reload NGINX and confirm that previous worker processes have exited. Assess the impact on clients that depend on HTTP/2. That measure does not replace the update; HTTP/2 can be re-enabled after patching.

The patch does not undo a prior compromise. The vendor has not published indicators of compromise.

Solution

The solution is to update NGINX Open Source to 1.30.7 (stable branch) or 1.31.9 (mainline branch), or later, and, on NGINX Plus, to 37.0.8.1 LTS or 37.3.0.1 CR, which cover both flaws (CVE-2026-123633 was already fixed in 37.0.7.1 LTS and 37.2.0.1 CR). Installations on R33 through R36 must move to one of those 37.x releases. Back up the configuration before updating. For NGINX Plus customers, the release notes and the vendor advisories are listed in Additional information.

For information on how to update, visit the following link:

https://nginx.org/en/download.html

Additional information: