F5 has issued software updates to address five critical vulnerabilities affecting NGINX, the widely deployed open-source web server, reverse proxy, and load balancer. Under specific configurations, the flaws allow attackers to achieve remote code execution with the privileges of an NGINX worker process.

The collection of issues, dubbed "NGINX2Root" by security firm Xint, includes two bugs that were also independently discovered and submitted by researchers from Rapid7, Wiz, Ikotas Labs, Palo Alto Networks, and Metnir. As reported by Help Net Security, there is currently no evidence showing that threat actors have leveraged the flaws in real-world attacks, and none appeared on the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog as of November 19.

Overview of the NGINX2Root Flaws

The reported vulnerabilities span several core NGINX features, including protocol handlers and internal utility modules. When Address Space Layout Randomization (ASLR) is bypassed or disabled, each of the five flaws can allow remote execution within the application worker context:

  • CVE-2026-123007 (NGINX2Shell): An integer underflow flaw within HTTP/2 flow control that triggers heap-based out-of-bounds read and write operations. The vulnerability can cause worker crashes and potentially execute arbitrary code.
  • CVE-2026-123633: A use-after-free issue present during HTTP/2 operations when traffic is forwarded directly to upstream destinations.
  • CVE-2026-123634: A use-after-free bug in the NGINX internal DNS resolver. Attackers can trigger this via crafted HTTP requests on servers that simultaneously implement resolver, request-derived proxy_pass, and mirror with mirror_request_body off directives.
  • CVE-2026-121810: A use-after-free condition caused by closing a QUIC connection during an active HTTP/3 request.
  • CVE-2026-113425: A use-after-free weakness located in the mail proxy module's auth_http handling path.

Exploit Constraints and Escalation Risks

While researchers at Xint and Wiz developed private proof-of-concept exploits across all five flaws, Rapid7 researcher Stephen Fewer published a technical analysis alongside a functional proof-of-concept for CVE-2026-123007. However, weaponizing the vulnerability carries significant operational hurdles.

According to Tenable researchers reviewing the Rapid7 exploit, successful execution requires a glibc memory-copy routine specific to x86-64 systems, approximately 128 gigabytes of HTTP/2 traffic, and a mechanism to defeat ASLR by parsing heap addresses from web server responses. Exploits are also unlikely to succeed against instances operating behind HTTP/2-terminating reverse proxies or across connections too slow to complete data transfer before reaching NGINX's standard one-hour connection timeout.

To escalate from the worker process to root privileges, Xint researchers chained the vulnerabilities with an unpatched use-after-free bug in the Linux kernel's SCTP code that leads to a double-free condition. Using that secondary flaw, researchers achieved root access on cloud hosts and broke out of Docker container environments. The kernel bug did not have an assigned CVE designation as of November 18.

Impacted Products and Vendor Response

F5 resolved the vulnerabilities in NGINX Open Source versions 1.30.7 and 1.31.9, as well as NGINX Plus versions 37.0.8.1 and 37.3.0.1. The vendor simultaneously addressed five additional lower-severity flaws in the same patch cycle.

Because NGINX underpins multiple commercial solutions, the vulnerabilities also touch downstream technologies such as NGINX Instance Manager, NGINX Ingress Controller, and NGINX Gateway Fabric. F5 has delivered patches for some of these products and continues development on updates for the remainder of its affected portfolio.

What You Should Do

Security and engineering teams should prioritize testing and deploying the official application upgrades across their infrastructure. Administrators must take the following steps to secure vulnerable environments:

  • Upgrade the software binary: Install NGINX Open Source 1.30.7 or 1.31.9, or update NGINX Plus to versions 37.0.8.1 or 37.3.0.1. Organizations relying on Linux distribution packages should verify and apply backported vendor fixes.
  • Perform a complete process restart: Administrators must execute a full restart of the NGINX service. Issuing a standard configuration reload is insufficient because it does not replace the running executable in memory.
  • Inspect HTTP/2 activity: Utilize guidance released by Xint researchers to monitor access logs and telemetry for signs of exploitation attempts targeting CVE-2026-123007.
  • Reduce external exposure: Enforce proxy termination ahead of origin servers, disable unused modules such as the mail proxy or experimental HTTP/3 support where unnecessary, and apply strict network segmentation around internet-facing hosts.