← All articles

NGINX vulnerability affects HTTP/2 servers, patches released

NGINX vulnerability affects HTTP/2 servers, patches released

The NGINX vulnerability CVE-2026-123007 can let an unauthenticated attacker run code on a server when HTTP/2 is enabled. HTTP/2 is a newer version of the web protocol used between browsers and web servers. The flaw, called “nginx2root”, has existed in the open-source NGINX code since version 1.9.5, released on September 22, 2015. F5, the company behind NGINX, released versions 1.31.9 and 1.30.7 today to correct it.

The flaw can result in code execution when ASLR, short for Address Space Layout Randomization, is disabled or bypassed. ASLR is a protection that makes important parts of a program appear at changing memory locations, making exploitation harder. Security researchers at Wiz said they bypassed ASLR and ran code in tests. Xint’s researchers said they achieved code execution using only a reachable HTTP/2 port. Neither F5 nor the Wiz and Rapid7 researchers has reported attacks exploiting the flaw so far, and CISA’s Known Exploited Vulnerabilities catalog did not list it as of today.

Code executed through the flaw initially has the permissions of an NGINX worker process, the part of NGINX that handles requests. Reaching root, the highest level of access on the host, requires a separate privilege escalation step, according to CIRCL, the Computer Incident Response Center Luxembourg. In Xint’s tests, a worker process reached root through a separate flaw in the Linux kernel’s SCTP code, including when NGINX was running inside a Docker container. SCTP is a network transport protocol, similar in purpose to TCP.

Every open-source NGINX release from 1.9.5 through 1.31.8 is vulnerable, according to NGINX security advisories. That includes 1.31.8 from October 21 and the security releases 1.31.7 and 1.30.6 from October 14. NGINX Plus is also affected, in 37.x releases before the fixed builds and in R34 through R36. Public proof-of-concept code is available on GitHub, although its notes say it is intended only to demonstrate the attack against a freshly started Docker container on the same machine.

The same releases address four additional flaws that F5 says can also lead to code execution under the same ASLR condition. All five flaws are scored 9.2 out of 10 under CVSS 4.0, a system for rating the severity of security vulnerabilities. CVE-2026-123633 requires HTTP/2, requests being passed to a backend server, and a worker running low on worker_connections. CVE-2026-123634 requires a proxied server name built from variables, together with a server-side include or mirror subrequest that looks up the same name. CVE-2026-121810 requires HTTP/3, while CVE-2026-113425 requires NGINX to be used as a mail proxy.

HTTP/2 is enabled when a listen directive includes http2 or when http2 on is configured. Administrators can check whether a server accepts it by running openssl s_client with -alpn h2. A response containing “ALPN protocol: h2” means HTTP/2 was accepted. If a CDN sits in front of NGINX, the origin server must be tested directly, because an origin that accepts only HTTP/1.1 cannot be attacked through HTTP/2.

For NGINX Open Source, versions 1.31.0 through 1.31.8 in the mainline branch are fixed by 1.31.9. Versions 1.9.5 through 1.30.6, including older branches such as 1.28, are fixed by 1.30.7. NGINX Plus 37.1.0 through 37.2.0.1 are fixed by 37.3.0.1, while 37.0.0 through 37.0.7.1 are fixed by 37.0.8.1. No fix is listed for NGINX Plus R34 through R36. NGINX release notes state that 1.31.9 and 1.30.7 correct all five flaws. On NGINX Plus, 37.3.0.1 and 37.0.8.1 fix four flaws, while the CVE-2026-123633 correction appeared earlier in 37.2.0.1 and 37.0.7.1.

A full restart or live binary upgrade is required after updating. A reload alone can leave the old executable running, and existing connections can remain on old worker processes. Official NGINX Docker images had 1.31.9 and 1.30.7 tags available as of today, including Alpine variants. Ubuntu and Debian had not shipped fixed packages as of today. Ubuntu’s CVE status page listed NGINX as vulnerable from Ubuntu 16.04 through 26.10, while Debian’s security tracker listed it as vulnerable in bookworm, trixie, forky and sid. Distribution packages can include a fix without changing the version shown by nginx -v, so administrators should compare the complete package version with the relevant distribution advisory.

Temporary measures are limited. For CVE-2026-123634, the vendor advises avoiding SSI and mirror directives and not building a proxied server name from variables. For CVE-2026-113425, listeners should be limited to trusted networks. CIRCL advises turning off HTTP/2 until an upgrade is possible. This blocks CVE-2026-123007 and CVE-2026-123633, but not the other three flaws. Where HTTP/3 is used, turning it off removes the setup required by CVE-2026-121810.

On NGINX 1.25.1 and later, administrators can set http2 off in each affected server block and remove http2 from listen directives. On versions 1.9.5 through 1.25.0, remove http2 from the listen directive, changing listen 443 ssl http2; to listen 443 ssl;. Restart NGINX where needed and repeat the OpenSSL check to confirm that HTTP/2 is no longer accepted. Until the Linux kernel SCTP flaw is fixed, CIRCL also advises hosts that do not use SCTP to block its kernel module from loading. Adding install sctp /bin/false to a .conf file in /etc/modprobe.d/ is one option, but it does not unload an already loaded module or disable SCTP built into the kernel.

CIRCL recommends watching for NGINX workers starting unexpected programs, abnormal worker exits or core dumps, long-lived HTTP/2 connections with heavy incoming traffic but few logged requests, and unusual outbound connections or DNS lookups. A clean access log does not rule out an attack because HTTP/2 control frames do not normally appear there as requests, and none of these signs proves exploitation by itself. Rapid7’s analysis says its attack required about 128 GB of HTTP/2 traffic and took two and a half minutes in a demonstration. On links slower than about 300 Mbit/s, the transfer would exceed NGINX’s default one-hour connection limit and fail. The method also depends on a glibc memory-copy routine selected on x86-64 CPUs with the avx512f and avx512vl features. Wiz tested official NGINX 1.31.7 and 1.31.8 builds using HTTP/2 over TLS on 64-bit systems, while Xint reported success against test servers on AWS, GCP and Azure, including through a public IP address.

For website owners who want a managed platform rather than to maintain the web server themselves, AEU Hosting provides managed WordPress hosting, secured end to end. The safest immediate action for NGINX administrators remains upgrading to a fixed release, or disabling the affected protocol temporarily where an upgrade cannot happen at once.

Also available in: DeutschItalianoShqip