Home / Blog / F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go…
Tech News

F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public

F5 patched five critical NGINX flaws carrying a 9.2 CVSS rating that allow unauthenticated attackers to execute remote code across nine million servers.

By Dillip Chowdary • Nov 19, 2026 • Source: SecurityWeek

F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public
Image: SecurityWeek

At a glance

Affected product
NGINX Open Source, NGINX Plus, BIG-IP
Patched versions
Open Source 1.30.7 and 1.31.9, Plus 37.0.8.1 and 37.3.0.1
Severity rating
CVSS 9.2 critical
Announcement date
Wednesday
Exploitation limits
Requires ASLR bypass and specific protocols
Known exploitation
None observed in the wild

F5 released software updates resolving 22 security vulnerabilities across its application delivery portfolio, including five critical defects in NGINX that permit unauthenticated remote code execution. Documented in SecurityWeek's report, the critical vulnerabilities carry a 9.2 CVSS score and jeopardize mail proxies, HTTP/3 endpoints, and standard static file servers.

This analysis examines the operational mechanics of the NGINX2Root vulnerabilities, emerging public exploit techniques, and the global attack surface across exposed enterprise infrastructure. System administrators, network security engineers, and DevOps teams managing NGINX Open Source or NGINX Plus environments should consult these findings to remediate vulnerable systems immediately.

01Five critical vulnerabilities across proxy protocols

The vulnerability cluster known as NGINX2Root encompasses CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634, each carrying a critical CVSS score of 9.2. These defects allow unauthenticated remote attackers to target foundational server operations across diverse deployment profiles. The flaws jeopardize installations handling mail traffic, modern web sessions, and backend proxy routing.

CVE-2026-113425 impacts instances operating as mail proxies when an attacker delivers crafted mail sessions to the host. For environments utilizing HTTP/3, CVE-2026-121810 triggers an exploitable use-after-free condition in the worker process. Additionally, CVE-2026-123634 compromises proxy servers when proxied server names contain variables and process subrequests from Server Side Includes or mirror directives.

Deployments with HTTP/2 enabled remain vulnerable to CVE-2026-123007 and CVE-2026-123633. Exploiting CVE-2026-123007 causes a buffer overflow, whereas triggering CVE-2026-123633 creates a use-after-free state in the worker process. Both vulnerabilities permit unauthorized attackers to execute shell commands with the operating privileges of the nginx worker process.

02Worker process compromise and container escape

Security researchers at Ikotas Labs, Metnir, Rapid7, Wiz, and Xint independently discovered and reported the two HTTP/2 vulnerabilities. Their investigations confirmed that successful exploitation allows attackers to execute commands under the nginx worker process privileges and compromise the server. Attackers leverage this foothold to gain interactive shell access inside target environments.

Testing conducted by Wiz demonstrated code execution on default installations delivering static files, requiring no backend application or external modules. The defect spans all releases since version 1.9.5 launched in 2015. Researchers at Xint chained CVE-2026-123007 with an unpatched Linux kernel bug to break out of a Docker container and secure root privileges.

Note: F5 stated that arbitrary code execution is only achievable if address space layout randomization is disabled or bypassed on the host operating system. Independent researchers observed that the buffer overflow and use-after-free conditions themselves permit attackers to leak memory addresses directly from server responses to defeat platform defenses.

03Network traffic thresholds and public exploits

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Rapid7 published proof-of-concept exploit code targeting CVE-2026-123007, noting that successful code execution demands transmitting approximately 128 gigabytes of HTTP/2 data. Depending on available network bandwidth, exploitation requires between two minutes and one hour. On slower network links, the default one-hour NGINX connection lifetime expires before attackers can complete the delivery.

Reverse proxies disrupt exploit delivery because intermediate network hops typically modify and reorder attacker-controlled HTTP/2 frames, breaking the conditions required for execution. Conversely, Censys researchers reproduced CVE-2026-123007 in laboratory tests using cleartext HTTP/2 without generating the massive traffic volume reported by Rapid7. Censys subsequently released its proof-of-concept code on GitHub.

| Research Team | Traffic Protocol | Volume Requirement | Exploit Window | | Rapid7 | Encrypted HTTP/2 | Approximately 128 GB | Two minutes to one hour | | Censys | Cleartext HTTP/2 | Minimal laboratory frames | Immediate reproduction |

Censys published its exploit demonstration to help security teams validate their detection posture against unencrypted HTTP/2 attacks. The research proves that determined attackers can bypass bandwidth limitations when targeting internal or cleartext service endpoints. Security teams cannot rely on network traffic anomaly thresholds alone to prevent exploitation.

04Nine million vulnerable servers worldwide

Global scanning data compiled by Censys illustrates the massive exposure facing internet-connected infrastructure running unpatched software. Scans identified approximately nine million NGINX services operating on vulnerable releases with HTTP/2 enabled. These publicly accessible servers remain directly susceptible to worker process compromise if network defenders delay patching.

Censys also observed 103 million additional NGINX services that suppress specific version numbers in their HTTP headers. A large percentage of these masked servers likely run affected software configurations that remain open to attack. Hiding server software banners provides no protection against memory corruption vulnerabilities.

05Official software patches and companion fixes

F5 resolved the security flaws across supported open-source and commercial branches of its software. Administrators running NGINX Open Source should update immediately to version 1.30.7 or version 1.31.9. Enterprise deployments utilizing NGINX Plus require updating to version 37.0.8.1 or version 37.3.0.1 to eliminate the remote execution pathways.

The release also patches five secondary NGINX defects that trigger connection termination, certificate verification bypasses, and worker process segmentation faults. Other fixed bugs cause denial-of-service conditions by trapping worker processes inside infinite loops. Applying the updates prevents external adversaries from degrading web server availability.

F5 deployed security fixes for 12 BIG-IP vulnerabilities alongside the NGINX updates, resolving critical and high-severity flaws that enable code execution, denial-of-service, file tampering, and token lifetime manipulation. F5 confirmed that none of the disclosed flaws have been exploited in active attacks.

Frequently asked questions

What are the NGINX2Root vulnerabilities?

NGINX2Root comprises five critical flaws tracked as CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634 with a 9.2 CVSS rating. They allow unauthenticated remote attackers to execute arbitrary code within the worker process.

Which versions of NGINX contain the official fixes?

Patches are available in NGINX Open Source versions 1.30.7 and 1.31.9, and NGINX Plus versions 37.0.8.1 and 37.3.0.1. The maintenance update also fixes five additional NGINX bugs and 12 BIG-IP flaws.

Can attackers achieve root access using these flaws?

Exploitation grants command execution under the nginx worker process, but researchers at Xint chained CVE-2026-123007 with a Linux kernel vulnerability to escape a Docker container and gain host root privileges. Code execution also requires bypassing or disabling ASLR.

How many internet-facing servers are affected by the flaws?

Censys identified approximately 9 million NGINX services running affected software with HTTP/2 enabled. An additional 103 million services do not expose their version numbers.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →