As reported by BleepingComputer, two critical NGINX vulnerabilities — tracked as CVE-2026-123007 and CVE-2026-123633 and collectively dubbed "nginx2root" — allow unauthenticated attackers to achieve remote code execution on exposed web servers. What elevates this beyond a routine patching cycle is the demonstrated chain to full root compromise via a Linux kernel SCTP flaw, effectively turning a web-tier bug into a host-takeover primitive.

Security Impact: As reported by BleepingComputer, two critical NGINX vulnerabilities — tracked as CVE-2026-123007 and CVE-2026-123633 and collectively dubbed "nginx2root" — allow unauthenticated attackers to achieve remote code execution on exposed web servers.

Why This Matters

NGINX is among the most widely deployed web servers and reverse proxies on the internet, powering a significant portion of the top million sites. These vulnerabilities are unauthenticated, require no application-level credentials, and affect configurations as mundane as serving static files over HTTP/2 with TLS — the default for many production deployments. The attack surface is enormous.

The first flaw, CVE-2026-123007, is a flow-control bug corrupting NGINX worker memory. It impacts every release from 1.9.5 (2015) through 1.31.8 — a decade-long exposure window. The second, CVE-2026-123633, is a use-after-free triggered when the worker exhausts HTTP/2 connection slots during request proxying, affecting versions 1.19.7 through 1.31.8. Both were independently discovered by Xint, Wiz, Ikotas Labs, Metnir, and Rapid7 — a rare convergence that signals the underlying logic is well understood by multiple research teams.

Vulnerability Summary

CVETypeSeverityAffected VersionsPatch Available
CVE-2026-123007Flow-control / memory corruptionCritical1.9.5 – 1.31.81.30.7 stable, 1.31.9 mainline
CVE-2026-123633Use-after-free (HTTP/2 proxy)Critical1.19.7 – 1.31.81.30.7 stable, 1.31.9 mainline
CVE-2026-121810Use-after-free (HTTP/3 reverse proxy)HighSee vendor advisory1.30.7 / 1.31.9
CVE-2026-123634Use-after-free (DNS subrequests)HighSee vendor advisory1.30.7 / 1.31.9
CVE-2026-113425Use-after-free (mail proxy auth)HighSee vendor advisory1.30.7 / 1.31.9
CVE-2026-118899DoS (TLS 1.3 infinite loop)HighSee vendor advisory1.30.7 / 1.31.9

Who Is at Risk

Who Is at Risk
Internet-facing NGINX servers with HTTP/2 enabled — the default for most modern TLS deployments.
Containerized NGINX workloads on Linux hosts with SCTP kernel modules loaded — the exact scenario Xint used to escape to root.
Reverse proxy configurations using HTTP/2 upstream connections, which trigger CVE-2026-123633.
Organizations on long-running stable branches that haven't tracked NGINX security releases since 2015-era deployments.
The decade-long exposure window for CVE-2026-123007 means legacy infrastructure — especially embedded appliances, load balancers shipping bundled NGINX, and long-lived container images — may remain vulnerable long after the upstream patch ships.

Shield53 Recommendations

Immediate Actions

  • Patch now: Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline). NGINX Plus customers should move to 37.0.8.1 or 37.3.0.1.
  • If patching is delayed: Disable HTTP/2 in your NGINX configuration (http2 off; or remove listen ... http2) as an interim mitigation for the nginx2root flaws. Note this does not address the other three CVEs.
  • Audit container hosts: Restrict SCTP module loading on Docker/Kubernetes nodes hosting NGINX containers. Use modprobe -r sctp and blacklist the module if not required, breaking the kernel-escape chain.
  • Inventory and asset discovery: Identify all NGINX instances — including those embedded in appliances, ingress controllers, and CI/CD-built images — using tools like nginx -v across your fleet.
  • Scan container images: Rebuild and republish any images bundling vulnerable NGINX versions. Prioritize public-facing ingress controllers (ingress-nginx, Traefik if it uses NGINX backend).
  • Detection: Monitor NGINX worker logs for abnormal restarts, segfaults, or unexpected child process spawning — indicators of memory corruption exploitation. Deploy runtime detection for SCTP socket creation from container namespaces.
  • Network-level hardening: Ensure WAF or load balancer layers rate-limit HTTP/2 stream creation to reduce the reliability of memory-corpression triggers.

Broader Implications

The nginx2root chain underscores a persistent blind spot: infrastructure software with decade-old code paths receiving security scrutiny only after years of deployment. The fact that five independent research teams identified overlapping flaws suggests the HTTP/2 implementation in NGINX deserves deeper systematic review — particularly around connection lifecycle and memory management under resource exhaustion. Organizations should treat this as a signal to evaluate whether other HTTP/2-capable servers in their stack have received comparable audit depth.

No public proof-of-concept exploits have been released by Wiz or Xint at this time, but given the breadth of researcher involvement and the simplicity of the trigger conditions (unauthenticated HTTP/2 requests), Shield53 assesses that functional exploits are likely to appear in the wild within weeks. Act now.