As reported by The Hacker News, a decade-old vulnerability in NGINX's HTTP/2 implementation allows unauthenticated attackers to achieve remote code execution on affected servers. The flaw, CVE-2026-123007 — dubbed "nginx2root" — has been present since NGINX version 1.9.5 (September 2015) and affects every open-source release through 1.31.8. F5 released fixed versions 1.31.9 and 1.30.7 on November 18, 2026, alongside patches for four additional RCE-class vulnerabilities.

Security Impact: As reported by The Hacker News, a decade-old vulnerability in NGINX's HTTP/2 implementation allows unauthenticated attackers to achieve remote code execution on affected servers.

This is a significant exposure window: eleven years of vulnerable NGINX deployments. HTTP/2 is widely enabled across the internet — it is the default protocol for modern web traffic and a standard configuration on performance-optimized servers. The attack surface is enormous.

Vulnerability Details

CVE IDCVSS 4.0Condition RequiredSeverity
CVE-2026-1230079.2HTTP/2 enabledCritical
CVE-2026-1236339.2HTTP/2 + backend proxy + low worker_connectionsCritical
CVE-2026-1236349.2Variable-based proxy server name + SSI/mirror subrequestCritical
CVE-2026-1218109.2HTTP/3 enabledCritical
CVE-2026-1134259.2NGINX used as mail proxyCritical

Affected Products

  • NGINX Open Source: Versions 1.9.5 through 1.31.8 (fixed in 1.31.9 and 1.30.7)
  • NGINX Plus: R34 through R36 and 37.x releases prior to today's fixed builds

Exploitation Status

No active exploitation has been reported by F5, Wiz, or Rapid7 as of the disclosure date. CISA's Known Exploited Vulnerabilities catalog does not currently list any of these CVEs. However, proof-of-concept code is publicly available on GitHub. While the published PoC is limited to demonstrating the attack against a freshly started Docker container on the same host, Wiz researchers have independently demonstrated ASLR bypass and code execution, and Xint researchers achieved RCE with only a reachable HTTP/2 port.

Why This Matters

Several factors elevate the risk profile beyond a typical RCE disclosure:

Why This Matters
Decade-long exposure: Any NGINX server with HTTP/2 enabled since 2015 has been vulnerable. That covers a vast number of production environments, container images, and legacy deployments.
No authentication required: The attack path needs only a reachable HTTP/2 port — no credentials, no application-level access.
ASLR is the primary barrier: F5 notes exploitation requires ASLR to be off or bypassable. Wiz has already demonstrated a bypass. Organizations relying on ASLR as a compensating control should not assume protection.
Worker-process to root escalation: While initial code execution runs as the NGINX worker user, CIRCL confirmed that combining this flaw with a separate Linux kernel SCTP bug can escalate to root — even from within a Docker container. Container isolation alone is insufficient.
Five CVEs, one patch day: The additional four flaws expand the attack surface to HTTP/3 deployments, mail proxy configurations, and specific proxy/SSI setups. Organizations must assess all five conditions.
The assumption that HTTP/2 is a safe, well-tested protocol layer is no longer valid for NGINX. Eleven years of vulnerable code means your environment was exposed long before today's advisory — not just starting today.

Who Is Most at Risk

  • Direct-exposed NGINX servers with HTTP/2 or HTTP/3 enabled and no CDN in front (or where the origin accepts HTTP/2 directly)
  • Containerized NGINX deployments — especially those running on hosts with vulnerable SCTP kernel code, where container escape to root is possible
  • NGINX Plus customers running R34–R36 or early 37.x builds
  • Hosting providers and CDNs running custom NGINX builds that may lag behind upstream releases
  • Mail proxy deployments using NGINX's mail proxy module (CVE-2026-113425)
  • Systems with ASLR disabled — including some embedded, legacy, or misconfigured production servers

Detection: Check if HTTP/2 Is Enabled

Run the following against your NGINX origin (not through a CDN):

openssl s_client -alpn h2 -connect your-origin:443

If the output includes ALPN protocol: h2, HTTP/2 is enabled and the server is vulnerable if unpatched. Also check NGINX config for listen ... http2 directives or the http2 on directive.

Immediate Actions

  • Patch immediately to NGINX 1.31.9 (mainline) or 1.30.7 (stable). NGINX Plus customers should apply the fixed builds released today.
  • If patching is delayed: Disable HTTP/2 and HTTP/3 by removing http2 from listen directives and setting http2 off. This degrades performance but eliminates the primary attack vector.
  • Audit for HTTP/2 exposure across all NGINX origins, including those behind CDNs. An origin that accepts only HTTP/1.1 is not vulnerable to CVE-2026-123007.
  • Update container images — rebuild any Docker images based on NGINX 1.9.5–1.31.8 and redeploy.
  • Validate kernel SCTP status — check whether the SCTP module is loaded on hosts running NGINX containers. Disable or restrict SCTP if not needed to reduce privilege escalation risk.
  • Review mail proxy usage — if NGINX is used as a mail proxy, prioritize patching for CVE-2026-113425 even if HTTP/2 is not enabled.

Shield53 Recommendations

  • Treat this as a critical-severity patch event. Five CVEs at 9.2 CVSS 4.0 with public PoC code is a high-urgency scenario. Establish a 72-hour patching SLA for internet-facing NGINX assets.
  • Inventory all NGINX instances — including sidecar containers, ingress controllers, and API gateways that embed NGINX. Many Kubernetes ingress controllers (e.g., ingress-nginx) bundle NGINX and may need separate patching cycles.
  • Do not rely on ASLR as a compensating control. Researchers have already demonstrated bypasses. Assume the RCE is achievable on any vulnerable instance with HTTP/2 reachable.
  • Assume potential prior compromise for high-value targets. The vulnerability has existed since 2015. If you operate critical infrastructure, consider whether threat actors may have already exploited this flaw. Review NGINX worker process logs, unexpected child process spawns, and anomalous outbound connections for the past 30–90 days.
  • Apply defense-in-depth: Ensure WAF rules, network segmentation, and egress filtering are in place. If exploitation occurs, these layers can limit lateral movement and data exfiltration.
  • Monitor for CISA KEV addition. Given the severity and public PoC, CISA may add these CVEs to the Known Exploited Vulnerabilities catalog. If added, federal agencies and many enterprises will have a binding remediation deadline.

The nginx2root disclosure is a reminder that widely deployed, mature software is not immune to deep-seated vulnerabilities. Eleven years of exposure means the question is not whether your NGINX servers were vulnerable — they were. The question is whether anyone exploited that window before today.