NGINX2Root CVE-2026-123007: HTTP/2 RCE Patch Guide

NGINX CVE-2026-123007 enables HTTP/2 worker-level RCE. Check affected versions, upgrade to 1.30.7 or 1.31.9, and apply safe temporary mitigations.

William OGOU
5 min read
Share
On this page7 sections

On 18 November 2026, NGINX patched a flaw listed in Common Vulnerabilities and Exposures (CVE) as CVE-2026-123007. An integer underflow in Hypertext Transfer Protocol version 2 (HTTP/2) flow control permits unauthenticated remote code execution (RCE) under specific conditions. The vulnerable code dates to 1.9.5; install 1.31.9 mainline or 1.30.7 stable, or a verified vendor backport.

F5’s Common Vulnerability Scoring System (CVSS) v4.0 score is 9.2, Critical; nginx.org rates the flaw major. Sources reviewed on 18 November 2026 identify laboratory exploitation, not confirmed in-the-wild attacks.

What to Remember

  • Patch the binary: A configuration reload cannot replace vulnerable executable code.
  • Check the origin: HTTP/2 must reach the unpatched NGINX listener.
  • Keep ASLR enabled: Address space layout randomisation (ASLR) helps, but researchers bypassed ASLR.
  • Respect boundaries: Worker RCE is not automatic host root; HTTP/2 shutdown is incomplete remediation.

How CVE-2026-123007 Enables Remote Code Execution

NGINX refunds flow-control credit when cancelling queued response data. A client can inflate the connection window before cleanup, pushing the refund beyond HTTP/2’s maximum. The next unsigned bounds check underflows, accepting further WINDOW_UPDATE frames.

On tested 64-bit builds, the oversized window becomes a negative response length, then an excessive memcpy() size in Transport Layer Security (TLS) output. Memory disclosure and corruption enable worker RCE, including on static-file servers.

A compromised worker can tamper with served content and access secrets available to that process.

Rapid7’s public proof of concept (PoC) achieved RCE in an official Linux/amd64 NGINX 1.31.8 Docker image. F5 requires ASLR to be disabled or bypassed for RCE. The HTTP/2 Bomb vulnerability is a separate denial-of-service issue.

Build conditions matter: Rapid7’s method depended on a specific GNU C Library (glibc) copy implementation and substantial traffic; the demonstration does not establish universal exploitability. A web application firewall (WAF) cannot repair the binary, and HTTP/2 termination at an intermediary only helps when malicious frames cannot reach the origin.

Affected and Fixed NGINX Versions

ProductAffected upstream versionsFirst fixed release
NGINX Open Source mainline1.31.0–1.31.81.31.9
NGINX Open Source older/stable1.9.5–1.30.61.30.7
NGINX Plus continuous37.1.0 to before 37.3.0.137.3.0.1
NGINX Plus long-term support37.0.0 to before 37.0.8.137.0.8.1

Compare distribution backports against the full package revision, not nginx -v alone. Older 1.28 deployments need migration or a verified backport. Rapid7 lists no fix for Plus R34–R36; F5’s CVE record also identifies R33. Confirm vendor guidance and migrate legacy Plus deployments to a fixed supported branch.

Patch NGINX or Temporarily Disable HTTP/2

Install trusted fixed packages, or rebuild and redeploy containers from verified fixed images. Hardened container images still require patch verification. Complete a full restart or supported live binary upgrade, not merely a reload.

On 1.25.1+, remove legacy listen ... http2 parameters and apply the following in every affected server block, including blocks sharing listening addresses:

nginx
listen 443 ssl;
http2 off;

On 1.9.5–1.25.0, remove http2 from listen 443 ssl http2;; omit the newer http2 off; directive. HTTP/2-dependent clients need compatibility testing.

bash
# On systemd hosts; restart disconnects clients and briefly interrupts service.
sudo nginx -t && sudo systemctl restart nginx

Check Application-Layer Protocol Negotiation (ALPN) on the NGINX origin, not only the content delivery network (CDN). Replace both example hostnames:

bash
openssl s_client -connect origin.example:443 \
  -servername service.example -alpn h2 </dev/null

ALPN protocol: h2 confirms negotiation, not exploitability. TLS failures are inconclusive. Verify every listener; an origin accepting only HTTP/1.1 does not expose the HTTP/2 path.

HTTP/2 shutdown also blocks CVE-2026-123633, a reverse-proxy use-after-free. CVE-2026-123634 affects Domain Name System (DNS) resolver processing; CVE-2026-121810 affects HTTP/3; CVE-2026-113425 affects mail proxying. Disabling HTTP/2 does not cover the latter three. November’s releases fix more than the five code-execution paths discussed here.

Xint’s nginx2root research chained worker RCE with a distinct Linux Stream Control Transmission Protocol (SCTP) kernel flaw for host root and container escape. Apply a kernel fix when the vendor provides one; disable unused SCTP where feasible.

Community Ingress-NGINX retirement requires migration to maintained controllers. Community kubernetes/ingress-nginx is separate from F5’s NGINX Ingress Controller.

Conclusion: Verify the Running Fix

My priority: patch reachable origins, verify every serving worker uses the fixed binary, and retain least-privileged worker accounts. Protocol shutdown buys time, not complete remediation.

Investigate unexpected worker crashes, worker-launched shells, and long-lived high-volume HTTP/2 connections. The warning signals are investigation leads, not proof of exploitation.

HTTP/2 control frames do not normally appear in access logs; clean logs do not establish safety.

To further enhance your cloud security and implement Zero Trust, contact me on LinkedIn Profile or [email protected].

FAQ

Frequently Asked Questions (FAQ)

Is CVE-2026-123007 actively exploited?

Reviewed sources report no confirmed in-the-wild exploitation on 18 November 2026. Rapid7 published a laboratory PoC.

Which NGINX versions fix CVE-2026-123007?

NGINX 1.30.7 stable and 1.31.9 mainline contain fixes. Verify distribution backports against the full package revision.

Does disabling HTTP/2 fix every nginx2root vulnerability?

HTTP/2 shutdown blocks CVE-2026-123007 and CVE-2026-123633. Resolver, HTTP/3, and mail proxy flaws require separate remediation.

Does CVE-2026-123007 immediately provide host root?

CVE-2026-123007 executes code with worker permissions. Xint demonstrated host root by additionally exploiting a distinct Linux SCTP flaw.

Is an NGINX reload sufficient after upgrading?

A configuration reload does not replace the running executable. Restart, redeploy containers, or complete a supported live binary upgrade.

Resources