Skip to main content
Emerging Threats

NGINX Flaw Exposes Servers to Unauthenticated Code Execution

Dimly lit server room with rows of rack-mounted servers and a single empty server rack in the foreground.

CVE-2026-123007 has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015 — a decade of exposure that the vendor and outside researchers say can let unauthenticated attackers run code on servers that accept HTTP/2.

The nginx2root flaw (CVE-2026-123007) and exploitability

F5, the company that maintains NGINX, has assigned the nickname "nginx2root" to CVE-2026-123007. According to vendor advisories and multiple research disclosures, the bug affects HTTP/2 handling and can allow an attacker to execute code without authentication when the server accepts HTTP/2 connections. F5 states the bug enables code execution where address space layout randomization (ASLR) is disabled or can be bypassed; security researchers at Wiz reported bypassing ASLR in their tests, and Xint reported running code against servers that simply had a reachable HTTP/2 port.

Code executed this way runs with the privileges of an NGINX worker process. CIRCL (Computer Incident Response Center Luxembourg) emphasizes that obtaining full root on the host requires a separate privilege-escalation path; in Xint's tests, a separate Linux kernel SCTP bug was used to reach root, even when NGINX ran inside a Docker container.

Which NGINX and NGINX Plus releases are fixed today

F5 published fixes in two branches today: NGINX Open Source mainline 1.31.9 and stable-branch 1.30.7. The vendor says every open-source release from 1.9.5 through 1.31.8 is vulnerable. On NGINX Plus, F5 lists fixes in 37.3.0.1 and 37.0.8.1 for four of the flaws, and earlier builds 37.2.0.1 and 37.0.7.1 received the specific CVE-2026-123633 fix; R34 to R36 currently show no fix listed.

The vendor's release notes say the two new open-source builds, 1.31.9 and 1.30.7, correct five related vulnerabilities — all scored 9.2 out of 10 on CVSS 4.0. After installing the fixed builds, administrators must fully restart NGINX or perform a live binary upgrade: a configuration reload alone can leave the old executable and worker processes in place, preserving vulnerable code for existing connections.

Operational mitigations: turning off HTTP/2 and blocking SCTP

CIRCL provides short-term mitigations for operators unable to upgrade immediately. Turning off HTTP/2 blocks CVE-2026-123007 and one related CVE-2026-123633; it does not mitigate the other three flaws. Where HTTP/3 is in use, CIRCL notes turning it off removes the setup required for CVE-2026-121810.

Concrete steps in NGINX configurations from CIRCL and the vendor:

  • On NGINX 1.25.1 and later, set http2 off; in each affected server block and remove http2 from listen directives.
  • On 1.9.5 through 1.25.0, remove http2 from the listen directive (for example, change listen 443 ssl http2; to listen 443 ssl;), then restart and verify with openssl s_client -alpn h2, which returns ALPN protocol: h2 if the server accepts HTTP/2.
  • Until the kernel SCTP bug is fixed, hosts not using SCTP should block the kernel module from loading by adding install sctp /bin/false to a file in /etc/modprobe.d/; this does not unload a loaded module or disable SCTP built into the kernel.

Proof-of-concept, exploitability constraints, and testing results from Wiz, Xint and Rapid7

Proof-of-concept code is publicly available on GitHub; its notes say it is suitable only for demonstrating the attack against a freshly started Docker container on the same machine. Research teams tested different exploit paths and documented constraints.

  • Wiz says it bypassed ASLR and ran code on official NGINX 1.31.7 and 1.31.8 builds using HTTP/2 over TLS on 64‑bit systems.
  • Xint reports executing code with nothing more than a reachable HTTP/2 port against test servers on AWS, GCP and Azure, including over a public IP address; Xint also used a Linux kernel SCTP bug in their chain to reach root.
  • Rapid7's demonstration required about 128 GB of HTTP/2 traffic and took roughly two and a half minutes; on links slower than about 300 Mbit/s the transfer would exceed NGINX's default one-hour connection limit and the attack would fail. Rapid7 also notes the method depends on a glibc memory-copy routine chosen on x86-64 CPUs that support avx512f and avx512vl.

As of today, neither the vendor nor Wiz, Rapid7 or Xint report observed exploitation in the wild, and CISA's Known Exploited Vulnerabilities catalog did not list the CVE.

What this means for cloud operators, distribution maintainers, and security teams

  • Cloud operators and service owners who expose an NGINX origin that accepts HTTP/2 should either upgrade to 1.31.9/1.30.7 or apply the CIRCL mitigations; test origins behind CDNs separately because an origin that accepts only HTTP/1.1 cannot be attacked through HTTP/2.
  • Linux distribution maintainers: Ubuntu and Debian had not shipped fixed packages as of today. Ubuntu's CVE status page lists nginx vulnerable across releases from 16.04 to 26.10; Debian's tracker lists bookworm, trixie, forky and sid as vulnerable. Distributors may backport fixes without changing the nginx -v output; operators should compare full package versions with distribution advisories.
  • Security teams should scan for the operational signs CIRCL lists — unexpected NGINX workers starting programs, worker crashes or core dumps, long-lived HTTP/2 connections with heavy incoming traffic but few logged requests, and unusual outbound connections or DNS lookups — remembering that a clean access log does not rule out exploitation because HTTP/2 control frames do not normally appear as logged requests.

The technical record here is unusually specific: a decade-old code path, multiple independent proof-of-concept tests, fixes published today and clear, limited mitigations. The narrow exploitation prerequisites — an HTTP/2-capable NGINX origin, particular CPU and kernel conditions, or a separate privilege-escalation bug — both constrain and complicate risk decisions for administrators. The immediate, concrete next step the vendor and multiple responders agree on is to install the published 1.31.9 or 1.30.7 builds or apply the documented mitigations until upgrades are possible.

Original story