Incident sheet · /security

Filed
Read
3 min · 598 words
Severity
Routine

NGINX2Root flaws expose 8.8 million servers to root takeover

Two unauthenticated HTTP/2 RCE flaws dubbed nginx2root put 8.8 million NGINX services at potential risk; one chains with a kernel bug for root access. Patches are out now.

Critical NGINX ‘NGINX2Root’ bugs let attackers hijack servers
FeedCritical NGINX ‘NGINX2Root’ bugs let attackers hijack servers — AI-generated

Event log

  1. Censys counted ~8.8 million NGINX services potentially exposed to CVE-2026-123007 as of November 19.
  2. CVE-2026-123007 affects NGINX 1.9.5 through 1.31.8, a range dating to 2015.
  3. Fixes shipped in NGINX Open Source 1.30.7 and 1.31.9; NGINX Plus 37.0.8.1 or 37.3.0.1.
  4. Roth's Shodan sampling found ~66% of NGINX HTTPS endpoints support HTTP/2.
  5. Over 511,000 exposed services have already been patched or mitigated.

Roughly 8.8 million NGINX services were potentially exposed to critical flaw CVE-2026-123007 as of November 19, according to Censys' live exposure tracker. Two unauthenticated HTTP/2 vulnerabilities, dubbed "nginx2root" by researchers, allow remote code execution on vulnerable servers, and one has been demonstrated chained with a Linux kernel bug to gain root on the host.

What are the two critical flaws?

CVE-2026-123007 is a flow-control bug that can corrupt memory in an NGINX worker process. It affects every version from 1.31.8 down to 1.9.5, a release lineage stretching back to 2015. Wiz demonstrated unauthenticated remote code execution on a server hosting ordinary static files over HTTP/2 with TLS.

Xint went further. The firm chained CVE-2026-123007 with a separate flaw in the Linux kernel's SCTP subsystem (a transport-layer protocol) to escape an NGINX Docker container and gain root privileges on the underlying host.

CVE-2026-123633 is a use-after-free bug (a defect where code references freed memory). It triggers when NGINX accepts HTTP/2 connections and proxies requests to a backend, affecting versions 1.19.7 through 1.31.8. When a worker runs low on connection slots, it can close an active connection and free memory a pending request still uses. Wiz also demonstrated RCE through this flaw but is withholding its proof-of-concept exploits.

The HTTP/2 flaws were found independently by researchers at Xint, Wiz, Ikotas Labs, Metnir and Rapid7. Xint discovered three additional RCE flaws.

What else did F5 fix?

F5 patched five flaws in total. Three are Xint discoveries:

  • CVE-2026-121810 — use-after-free in HTTP/3 reverse proxying
  • CVE-2026-123634 — use-after-free in DNS resolution with subrequests
  • CVE-2026-113425 — use-after-free in mail proxy authentication

The update also addresses five vulnerabilities not covered in the Wiz or Xint reports. The most notable is CVE-2026-118899, a high-severity issue letting an unauthenticated attacker force a worker into an infinite loop while reading a request body over TLS 1.3, causing denial of service.

Censys reproduced the underlying memory corruption conditions in four of the five flaws in lab testing but did not achieve remote code execution.

What should administrators do now?

Upgrade immediately. Fixes shipped in NGINX Open Source 1.30.7 stable and 1.31.9 mainline. NGINX Plus users should move to 37.0.8.1 or 37.3.0.1. Where an upgrade is not yet possible, disabling HTTP/2 temporarily mitigates the two nginx2root flaws — but only those two.

Actual exposure requires an unpatched server with HTTP/2 enabled on a reachable listener; CVE-2026-123633 additionally requires proxying to a backend.

How real is the risk?

Security researcher Florian Roth said the flaws are worse than Node2Shell and Java2Shell but do not appear to be an imminent threat for most NGINX deployments. Commenting on X, Roth said the flaws are exploitable in non-default configurations, and warned that claims of widespread exposure based solely on version numbers are misleading.

Xint previously reported 98.9% of NGINX hosts disclosing recognizable versions ran software in the affected range. That figure ignores whether HTTP/2 is enabled or fixes have been backported. Roth scanned a few hundred NGINX HTTPS endpoints from Shodan and found roughly 66% support HTTP/2, but confirming exposure requires checking configuration and backport status.

Censys reports more than 511,000 previously exposed services have already been patched or mitigated. Another 104 million NGINX services do not disclose their versions, leaving their exposure undetermined.

via bleepingcomputer.com (Source)

Filed under

  • nginx
  • http-2
  • cve-123007
  • cve-123633
  • remote-code-execution
Share this article:

More from Rebecca Stone

Rebecca Stone

Show full bio

Senior reporter covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

195 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous article