Protect.Computer
NEWS

NGINX2Root: HTTP/2 Flaw CVE-2026-123007 Allows Code Execution

· 3 min read · Got hacked Network safety
NGINX2Root: HTTP/2 Flaw CVE-2026-123007 Allows Code Execution

Researchers at Xint have disclosed “NGINX2Root,” a set of five flaws in the NGINX web server that can let an unauthenticated attacker run commands with the privileges of an NGINX worker process. The broadest one, CVE-2026-123007, is a memory-corruption bug in NGINX’s HTTP/2 flow control, and it has been in the open-source code since version 1.9.5, released in 2015, according to The Hacker News. The other four need more specific setups: HTTP/3, requests proxied to a backend while NGINX is short on connections, a resolver-based proxy name used with a subrequest, or the mail proxy module.

Getting from a worker process to root on the host takes a second bug. Xint and the Luxembourg CERT (CIRCL) describe a separate Linux kernel flaw in the SCTP code that can be chained with NGINX2Root, including out of a Docker container. The Hacker News says neither the vendor nor the Wiz and Rapid7 researchers have reported attacks in the wild, and that CISA’s Known Exploited Vulnerabilities catalog did not list the flaw as of November 18. A public proof-of-concept exists on GitHub; The Hacker News says its notes limit it to demonstrating the attack against a freshly started Docker container on the same machine, and that Rapid7’s version needs about 128 GB of HTTP/2 traffic.

On whether an attacker needs ASLR to be off, the sources differ in emphasis. The Hacker News relays F5’s statement that code can run where ASLR is disabled or can be bypassed, and says Wiz bypassed it in tests. CIRCL’s guidance says turning ASLR off is not a prerequisite, because Xint’s report documents address-disclosure techniques, so it should not be treated as a stand-alone mitigation.

How to check if you’re affected

Affected versions of NGINX Open Source for CVE-2026-123007 are 1.9.5 through 1.31.8, per the advisory list at nginx.org; the other four flaws have different start versions, listed there too. Fixed releases are 1.31.9 (mainline) and 1.30.7 (stable). The Hacker News relays F5’s NGINX Plus table: 37.1.0 to 37.2.0.1 is fixed in 37.3.0.1, 37.0.0 to 37.0.7.1 is fixed in 37.0.8.1, and for R34 to R36 no fix is listed. F5’s own advisory page (K000163926) did not render for us, so the Plus figures are as reported by The Hacker News.

  • HTTP/2 exposure: The Hacker News says HTTP/2 is on where a listen directive includes http2 or http2 on; is set, and that running openssl s_client with -alpn h2 against the server prints ALPN protocol: h2 if it accepts HTTP/2. Behind a CDN, test the NGINX origin itself.
  • Distribution packages: The Hacker News reported that Ubuntu and Debian had not shipped fixed packages as of November 18 and that a patched package can keep the same version number nginx -v reports, so compare the full package version with your distribution’s advisory. Official Docker Hub tags for 1.30.7 are listed.
  • Temporary mitigation: CIRCL says removing http2 from listen (or http2 off; on 1.25.1 and later) blocks only the CVE-2026-123007 and CVE-2026-123633 paths, can break gRPC and other HTTP/2-only apps, and is not a complete fix. The same guidance covers the other flaws: avoid request-derived proxy names with subrequests, disable QUIC/HTTP/3 if affected, and restrict mail-proxy access.
  • After upgrading: CIRCL says to restart NGINX or use a supported binary upgrade; a reload leaves the old executable and old workers running.
  • Kernel escalation path: On hosts that do not use SCTP, CIRCL suggests blocking the module with install sctp /bin/false in a /etc/modprobe.d/ file. That does not unload a module that is already loaded or disable SCTP built into the kernel.
  • Signs of attack: The Hacker News, citing CIRCL, lists workers starting unexpected programs, abnormal worker exits or core dumps, long-lived HTTP/2 connections with heavy traffic but few logged requests, and unusual outbound connections. None is proof alone, and a clean access log does not rule out an attack.

One severity note: The Hacker News says F5 scores all five flaws 9.2 on CVSS 4.0, while nginx.org’s own advisory list labels CVE-2026-123007 and CVE-2026-113425 “major” and the other three “medium.” CIRCL’s page, written before the release, said the upstream fix was scheduled for November 19; nginx.org’s list and Docker Hub already show 1.31.9 and 1.30.7.

Related earlier coverage: F5 Ships Out-of-Band Patches for 3 Critical NGINX Flaws. Those were different CVE ids.

Sources

Related reading