10-year-old NGINX HTTP/2 flaw allows unauthenticated attackers to execute code on servers

A defect in NGINXHTTP/2 support may allow an attacker to execute code on servers that have HTTP/2 enabled, without needing to log in.

The ten-year-old defect, CVE-2026-123007, nicknamed “nginx2root,” has been present in the NGINX open source code since version 1.9.5, released on September 22, 2015. Patched versions 1.31.9 and 1.30.7 were released today.

F5the company behind NGINX, claims that attackers can execute code where ASLR is disabled or can be bypassed. Security researchers at Ace said they bypassed ASLR and executed code through the flaw during testing. Xint researchers said they executed code with nothing more than an accessible HTTP/2 port.

Code executed in this way gains permissions from an NGINX worker process. Getting root on the host takes a second way of escalating privileges, according to CIRCL, the Computer Incident Response Center Luxembourg.

In Xint’s tests, code running as a worker could gain root on the host via a separate bug in the Linux kernel’s SCTP code, even when NGINX was running in a Docker container.

Neither the vendor nor Wiz and Rapid7 researchers have reported any attacks exploiting this flaw so far. CISA’s Catalog of Known Exploited Vulnerabilities has not listed it to date.

The proof-of-concept code for the flaw is publicly available on GitHub, but its notes indicate that it is only suitable for demonstrating the attack against a freshly started Docker container on the same machine.

Every open source version from 1.9.5 to 1.31.8 is vulnerable, according to NGINX security advisories. This includes version 1.31.8 from October 21, as well as security versions 1.31.7 and 1.30.6 from October 14.

Wiz PoC

NGINX Plus is also affected in versions 37.x prior to patched releases and in versions R34 through R36, depending on the vendor’s advisory.

Today’s releases also fix four other flaws that the vendor says can lead to code executing under the same ASLR conditions. All five of them score 9.2 out of 10 on CVSS 4.0.

Each flaw can only be reached in a particular configuration:

DefaultWhat he needs
CVE-2026-123007HTTP/2 enabled
CVE-2026-123633HTTP/2, with requests forwarded to a backend server while the worker runs out of resources worker_connections
CVE-2026-123634A proxy server name constructed from variables, plus a server-side inclusion (SSI) or mirror subquery to a location that searches for the same name
CVE-2026-121810HTTP/3 enabled
CVE-2026-113425NGINX used as email proxy

HTTP/2 is enabled where a listen the directive includes http2or where http2 on is set. Running openssl s_client with -alpn h2 against a server indicates whether it accepts HTTP/2: the output indicates ALPN protocol: h2 if so. Behind a CDN, test the NGINX origin itself, because an origin that only accepts HTTP/1.1 cannot be attacked over HTTP/2.

Fixes, workarounds and signs of attack

These versions fix CVE-2026-123007, according to F5:

  • NGINX Open Source 1.31.0 to 1.31.8 (mainline): fixed in 1.31.9
  • NGINX Open Source 1.9.5 to 1.30.6, including older branches such as 1.28: fixed in 1.30.7
  • NGINX Plus 37.1.0 to 37.2.0.1: fixed in 37.3.0.1
  • NGINX Plus 37.0.0 to 37.0.7.1: fixed in 37.0.8.1
  • NGINX Plus R34 to R36: No fixes listed

Versions 1.31.9 and 1.30.7 fix all five flaws, according to the NGINX release notes. On NGINX Plus, 37.3.0.1 and 37.0.8.1 fix four of the flaws, and the CVE-2026-123633 fix was introduced in previous versions 37.2.0.1 and 37.0.7.1.

After upgrading, restart NGINX completely or use its live binary upgrade. A reload alone leaves the old executable running and existing connections can remain on old worker processes.

The official Docker images for NGINX to date have had tags 1.31.9 and 1.30.7, including Alpine variants.

Ubuntu and Debian have not delivered patched packages to date. The Ubuntu CVE status page listed nginx as vulnerable in its versions from 16.04 to 26.10, and the Debian security tracker listed it as vulnerable in bookworm, trixie, forky, and sid. A distribution package can contain a hotfix without changing the version number that nginx -v reports, so compare the full package version with the distribution’s own review.

PoC Xint

The vendor lists workarounds for only two of the five flaws. For the resolver flaw, CVE-2026-123634, avoid SSI and mirror directives and don’t construct proxy server name from variables. For the email proxy vulnerability, CVE-2026-113425, limit listeners to trusted networks.

CIRCL’s answer guidance states disabling HTTP/2 as a temporary mitigation until you can upgrade. This blocks CVE-2026-123007 and CVE-2026-123633, but not the other three flaws. Disabling HTTP/3 where it is used removes the configuration CVE-2026-121810 requires.

On NGINX 1.25.1 and later, set http2 off; in each person concerned server block and delete http2 of his listen guidelines. On versions 1.9.5 to 1.25.0, remove http2 of the listen directive, therefore listen 443 ssl http2; becomes listen 443 ssl;. Then restart NGINX if necessary and rerun the openssl check to confirm that the server no longer accepts HTTP/2.

Until the Linux kernel SCTP bug is fixed, the same instructions advise hosts not using SCTP, a network transport protocol like TCP, to block loading of its kernel module. One way is to add the line install sctp /bin/false to one .conf drop in /etc/modprobe.d/. This does not unload an already loaded module or disable in-kernel SCTP.

To detect signs of an attack, CIRCL suggests looking for NGINX workers that start unexpected programs, workers that terminate abnormally or exit core dumps, long-running HTTP/2 connections with lots of inbound traffic but few logged queries, 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. None of these signs constitutes proof in itself.

Rapid7’s version of the attack requires approximately 128 GB of HTTP/2 traffic, according to its technical analysis. The attack demonstration lasted two and a half minutes. On links slower than around 300 Mbps, the transfer would exceed NGINX’s default one-hour connection limit and the attack would fail.

The method also depends on a chosen glibc memory copy routine on x86-64 processors with the avx512f And avx512vl features.

Wiz ran its tests on official NGINX versions 1.31.7 and 1.31.8, using HTTP/2 over TLS on 64-bit systems, according to its disclosure post.

Xint’s attack worked against its test servers on AWS, GCP and Azure, including on a public IP address, according to its research report.

Gn tech

Logo