Skip to content
The Cybersecurity Focus
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
CVEexploitRCE

NGINX HTTP/2 Flaw Enables Unauthenticated RCE

By ogwatermelon
November 19, 2026 6 Min Read
0
November 18, 2026

CVE-2026-123007, a decade-old memory corruption flaw in NGINX HTTP/2 flow control, allows unauthenticated attackers to run code on any server with HTTP/2 enabled. F5 and the NGINX project released fixed builds today, and researchers from Wiz, Rapid7, and Xint have all demonstrated working remote code execution against the flaw, dubbed “nginx2root.”

What Happened: CVE-2026-123007 NGINX HTTP/2 Flaw Enables Unauthenticated RCE

First, F5, the company behind NGINX, disclosed CVE-2026-123007 on November 18, 2026, along with four related vulnerabilities that the vendor says can also lead to code execution under the same conditions. The vendor scored all five flaws 9.2 out of 10 under CVSS 4.0. The lead flaw is rated major and classified as memory corruption in HTTP/2 flow control.

Moreover, the vulnerability has existed since NGINX 1.9.5, which shipped on September 22, 2015. That means every open-source release from 1.9.5 through 1.31.8 is vulnerable, including the security releases 1.31.7 and 1.30.6 published on October 14, 2026. Fixed versions 1.31.9 and 1.30.7 are available today.

However, no exploitation has been reported yet. Neither F5 nor the three research teams said they have seen the flaw used in the wild, and CISA has not added it to the Known Exploited Vulnerabilities catalog as of today. However, public proof-of-concept code is already published on GitHub, so defenders should treat the window for patching as short.

Technical Details of the NGINX HTTP/2 Remote Code Execution Flaw

CVE-2026-123007 is an integer underflow in NGINX HTTP/2 flow control handling. An attacker who can reach the HTTP/2 port can corrupt worker process memory and achieve code execution with the privileges of the NGINX worker process. No authentication is required.

The exploit path depends on a handful of specific conditions:

  • Entry point: A reachable HTTP/2 listener, either through http2 on in a server block or listen 443 ssl http2
  • Privilege level: Code runs as the NGINX worker process user, not root
  • ASLR condition: F5 says exploitation works where ASLR is off or can be bypassed; Wiz demonstrated an ASLR bypass, and Xint said a reachable HTTP/2 port alone was sufficient in its tests
  • Data volume: Rapid7’s variant requires roughly 128 GB of HTTP/2 traffic, completing in about two and a half minutes in the demonstration
  • Hardware dependency: The Rapid7 method relies on a glibc memory-copy routine selected on x86-64 CPUs with AVX512F and AVX512VL

Furthermore, CIRCL, the Computer Incident Response Center Luxembourg, notes that escalation to root usually requires a second bug. In Xint’s testing, a worker-level compromise reached host root through a separate flaw in the Linux kernel’s SCTP code, even when NGINX ran inside a Docker container.

Five Related NGINX Flaws Fixed Today

In addition, the November 18 releases address five flaws that can each lead to code execution under the same ASLR condition. Each one requires a distinct configuration to reach:

  • CVE-2026-123007: Memory corruption in HTTP/2 flow control, requires HTTP/2 enabled
  • CVE-2026-123633: Use-after-free in HTTP/2, requires HTTP/2 plus requests proxied to a backend while the worker is low on worker_connections
  • CVE-2026-123634: Use-after-free in the resolver, requires a proxied server name built from variables plus an SSI or mirror subrequest
  • CVE-2026-121810: Use-after-free in HTTP/3, requires HTTP/3 enabled
  • CVE-2026-113425: Use-after-free in the mail proxy module, requires NGINX used as a mail proxy

How to Check if Your Server Is Exposed

Also, HTTP/2 is enabled where a listen directive includes http2 or where http2 on is set. You can confirm exposure by running openssl s_client -alpn h2 against the server. The output reads ALPN protocol: h2 if HTTP/2 is accepted.

If you sit behind a CDN, test the NGINX origin itself. An origin that accepts only HTTP/1.1 cannot be attacked through this vector, even when the edge supports HTTP/2.

Business and Operational Impact

NGINX is one of the most widely deployed web servers in the world, and it typically runs in a privileged position in the stack. The consequences of a compromised NGINX host extend well past the web tier.

  • Server compromise with attacker code running as the NGINX worker process on every exposed instance
  • Container escape risk when NGINX runs in Docker, since a worker-to-root path exists via the separate Linux SCTP bug
  • Data interception and tampering because NGINX terminates TLS and proxies live traffic, including session cookies and credentials
  • Long-lived blind compromise since HTTP/2 control frames do not normally appear in access logs, so a clean log does not rule out an attack
  • Supply chain blast radius since NGINX sits in front of internal APIs, databases, and cloud control planes
  • Patch delay risk because Ubuntu and Debian had not shipped fixed packages as of today, and distribution packages can carry fixes without changing the reported nginx -v version

Mitigation and Recommendations

Therefore, defenders should act quickly. The vendor lists workarounds for only two of the five flaws. For the resolver flaw CVE-2026-123634, avoid SSI and mirror directives and do not build proxied server names from variables. For the mail proxy flaw CVE-2026-113425, limit listeners to trusted networks.

Immediate Actions for Defenders

  1. Upgrade to NGINX 1.31.9 or 1.30.7, which fix all five flaws, or to NGINX Plus 37.3.0.1 or 37.0.8.1
  2. Fully restart NGINX after upgrading, or use the live binary upgrade, because a reload alone leaves the old executable running
  3. If patching must wait, disable HTTP/2: set http2 off in each affected server block on NGINX 1.25.1 and later, or remove http2 from the listen directive on 1.9.5 through 1.25.0
  4. Disable HTTP/3 where it is used to remove the setup required by CVE-2026-121810
  5. Block the SCTP kernel module from loading with install sctp /bin/false in a file under /etc/modprobe.d/ until the kernel bug is fixed
  6. Compare your full distribution package version against the vendor advisory, rather than relying on the version reported by nginx -v

Hunting for Signs of Compromise

Finally, CIRCL recommends several checks against any server that was reachable over HTTP/2:

  • NGINX workers starting unexpected child programs
  • Workers exiting abnormally or leaving core dumps
  • Long-lived HTTP/2 connections with heavy incoming traffic but very few logged requests
  • Unusual outbound connections or DNS lookups originating from the NGINX host

None of these indicators is proof on its own, and a clean access log does not clear the host. Note also that NGINX Plus releases R34 through R36 have no listed fix for CVE-2026-123007, so customers on those branches need to plan a migration path.

Bottom line: The CVE-2026-123007 NGINX HTTP/2 flaw is the most consequential NGINX weakness in over a decade, and public proof-of-concept code already exists even though no active exploitation is confirmed. Upgrade to 1.31.9 or 1.30.7 and fully restart every NGINX instance today, or disable HTTP/2 until you can.

Incident Summary

CVE ID: CVE-2026-123007 (CVSS 9.2, CVSS 4.0), known as “nginx2root”
Root Cause: Integer underflow leading to memory corruption in HTTP/2 flow control handling
Affected Systems: NGINX Open Source 1.9.5 through 1.31.8; NGINX Plus 37.x before 37.3.0.1 and 37.0.8.1, plus releases R34 through R36
Also Fixed: CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425
Disclosure Date: November 18, 2026
Patch Status: Available: NGINX 1.31.9 and 1.30.7 released November 18, 2026; distribution packages pending
Exploitation Status: No confirmed attacks; public proof-of-concept code available; not in CISA KEV as of November 18, 2026

References

  1. The Hacker News, “10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers,” November 18, 2026, https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html (accessed November 18, 2026)
  2. NGINX, “nginx security advisories,” https://nginx.org/en/security_advisories.html (accessed November 18, 2026)
  3. F5, “CVE-2026-123007 Advisory (K000163926),” https://my.f5.com/manage/s/article/K000163926 (accessed November 18, 2026)
  4. CIRCL, “Technical Response: NGINX HTTP/2 Vulnerabilities (tr-105),” https://www.circl.lu/pub/tr-105/ (accessed November 18, 2026)
  5. Wiz, “NGINX HTTP/2 RCE vulnerabilities,” https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities (accessed November 18, 2026)
  6. Rapid7, “CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE,” https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/ (accessed November 18, 2026)
  7. Xint, “nginx2root: Remote Code Execution,” https://xint.io/blog/nginx2root-remote-code-execution (accessed November 18, 2026)
  8. National Vulnerability Database, “CVE-2026-123007,” https://nvd.nist.gov/vuln/detail/CVE-2026-123007 (accessed November 18, 2026)

Tags:

CVEExploitRCE
Author

ogwatermelon

Follow Me
Other Articles
Previous

Helix Ransomware Attacks Sonoco

Next

CISA Confirms Active Exploitation of Critical Puppet Deserialization Flaw

AI Android Backdoor Botnet Breach Cloud CVE Exploit Hack Incident Infostealer KEV Linux Mac Malware Network News Phishing Ransomware RCE supp supply chain Virtualization Vishing Vulnerability Windows World Worm Zero Day

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026

Categories

  • AI
  • Android
  • Apple
  • Backdoor
  • BotNet
  • Breach
  • Cloud
  • CVE
  • exploit
  • Hack
  • Incident
  • Infostealer
  • KEV
  • Linux
  • Mac
  • Malware
  • News
  • Phishing
  • Ransomware
  • RCE
  • supply-chain
  • Uncategorized
  • Virtualization
  • Vishing
  • Vulnerabilities
  • Vulnerability
  • Windows
  • World
  • Worm
  • Zero Day
Copyright 2026 — The Cybersecurity Focus. All rights reserved.