Threat Intelligence

Decade-Old NGINX HTTP/2 Flaw Allows Remote Code Execution Without a Login: Patch and Restart Now

The Hacker News · 19 Nov 2026
Key Takeaway Upgrade NGINX to 1.31.9 or 1.30.7 and fully restart it, or switch off HTTP/2 until you can.

NGINX has fixed a serious flaw that has sat in its HTTP/2 support since version 1.9.5, released in September 2015. The bug, CVE-2026-123007 (nicknamed "nginx2root"), can let an attacker run code on a server with HTTP/2 enabled without logging in. F5, the company behind NGINX, says this works where ASLR, a memory protection feature, is turned off or can be bypassed. Wiz researchers said they bypassed ASLR in tests, and Xint's researchers said they ran code with only a reachable HTTP/2 port.

The code runs with the permissions of an NGINX worker process, not as root. Xint showed that a separate Linux kernel bug in SCTP could be used to reach root, even when NGINX ran inside a Docker container. No attacks have been reported by the vendor, Wiz or Rapid7, and the flaw was not in CISA's Known Exploited Vulnerabilities catalog at the time of writing. Proof-of-concept code is public on GitHub. Four further flaws, each scored 9.2 out of 10 on CVSS 4.0, were fixed in the same release.

Every open-source release from 1.9.5 through 1.31.8 is affected, as are NGINX Plus 37.x and R34 to R36 builds before the fixes. Versions 1.31.9 and 1.30.7 fix all five flaws. Official Docker images carry the new tags, but Ubuntu and Debian had not shipped fixed packages when the story was published. After upgrading, NGINX needs a full restart or live binary upgrade, because a reload leaves the old executable running.

If you cannot upgrade yet, turning off HTTP/2 is a temporary mitigation for CVE-2026-123007 and CVE-2026-123633, though not the other three flaws. Rapid7's version of the attack needs about 128 GB of HTTP/2 traffic and depends on particular CPU features, which limits it. Defenders should still watch for workers starting unexpected programs, abnormal worker crashes, and unusual outbound connections. A clean access log does not rule out an attack.

Why it matters

Anyone running internet-facing NGINX with HTTP/2 is exposed, and the assumption that a worker-level compromise is contained is weakened by the demonstrated kernel escalation to root, even from a Docker container. Distribution packages may be fixed without a changed version number, and a reload leaves old code running, so teams can believe they are patched when they are not. Clean access logs are also no proof of safety, because HTTP/2 control frames do not normally appear there as requests.

What to do

  • Upgrade open-source NGINX to 1.31.9 or 1.30.7, or NGINX Plus to the fixed builds, then fully restart or use live binary upgrade.
  • Run openssl s_client with -alpn h2 against each NGINX origin, including those behind a CDN, to see whether it accepts HTTP/2.
  • Turn off HTTP/2 in affected server blocks as a temporary mitigation, then rerun the openssl check to confirm.
  • Block the SCTP kernel module on hosts that do not use SCTP, and hunt for workers starting unexpected programs or crashing abnormally.
NGINX CVE-2026-123007 HTTP/2 remote code execution patch management

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.