Researchers Reproduce Unauthenticated RCE in nginx HTTP/2 Flaw CVE-2026-123007

· Original article ↗

Summary

Researchers reproduced worker crashes and code execution through CVE-2026-123007, an nginx HTTP/2 flow-control flaw. nginx 1.31.9 and 1.30.7 fix it; no in-the-wild exploitation was reported as of November 20, 2026.

Key points

  • A double refund of queued HTTP/2 data can push nginx’s connection window past its maximum; unsigned arithmetic then permits an oversized memory copy that corrupts memory.
  • The public exploit ran commands as the nginx worker without credentials. It requires reachable HTTP/2, substantial bandwidth, an idle server, and an x86-64 CPU with AVX-512; a separate PoC crashed workers without AVX-512.
  • Testing reproduced crashes and code execution against nginx 1.31.8. The PoC could not trigger the overflow on fixed version 1.31.9.
  • Affected upstream versions are nginx 1.9.5 through 1.31.8 with HTTP/2 enabled. Upstream fixes are in 1.31.9 and 1.30.7, with distribution-specific backports also listed.
  • If patching is not possible, disabling HTTP/2 blocks this flaw, though it also breaks gRPC through nginx. The article says RHEL 8, 9, and 10 had no fixed nginx packages as of November 20, 2026.
  • The article identifies possible exploitation indicators, including large single-connection traffic, bursts of HEAD requests, and nginx worker exits on signals 6 or 11.

Article Details

Attack Vectors
  • An unauthenticated attacker can send crafted HTTP/2 flow-control frames to a reachable nginx server with HTTP/2 enabled, triggering an integer underflow and memory corruption.
  • The published exploit requires a direct connection, an otherwise idle server, and about 119 GiB of bandwidth within nginx's one-hour connection limit; the demonstrated code-execution exploit also requires an x86-64 CPU with AVX-512. AVX-512 is not required to trigger a worker crash.
  • The article reports that the bug can be triggered over unencrypted HTTP/2 and does not require TLS. A reverse proxy that terminates HTTP/2 may disrupt the published exploit's expected frame behavior.
Defensive Notes
  • Upgrade nginx to 1.31.9 or 1.30.7, or install the fixed package from the relevant distribution. Restart nginx after upgrading; a configuration reload alone does not replace the running binary.
  • If patching is not possible, disable HTTP/2 and verify that the server negotiates HTTP/1.1. The article says this blocks both HTTP/2 nginx2root bugs, but also breaks gRPC through nginx.
  • For affected RHEL 8, 9, and 10 packages with no fix reported as of November 20, 2026, the article recommends disabling HTTP/2 until fixed packages are available.
  • Monitor nginx error logs for worker exits on signals 11 or 6, unusually large bytes_received on a single connection, bursts of HEAD requests, and programs started by the nginx worker. Treat these as possible exploitation indicators, not confirmation.
  • The article says per-IP connection limits and reverse proxies are not fixes. It also notes that distribution backports may retain upstream version strings, so verify package versions against distribution advisories.

MITRE ATT&CK

CVE

Vendors

Products

Tools

Countries

Related Articles