Home / Blog / Critical NGINX ‘NGINX2Root’ bugs let attackers hijack…
Tech News

Critical NGINX ‘NGINX2Root’ bugs let attackers hijack servers

F5 patched two critical NGINX HTTP/2 flaws that allow remote code execution and container escapes to root across millions of unpatched web servers.

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

Critical NGINX ‘NGINX2Root’ bugs let attackers hijack servers
Image: BleepingComputer

At a glance

Product
NGINX Open Source and NGINX Plus
Fixed versions
1.30.7, 1.31.9, 37.0.8.1, 37.3.0.1
Key flaw
CVE-2026-123007
Proxy flaw
CVE-2026-123633
Patch date
November 19, 2026
Exposed hosts
8.8 million services

F5 released security updates addressing two critical vulnerabilities dubbed nginx2root that allow unauthenticated attackers to execute arbitrary code remotely on servers running NGINX. As detailed in BleepingComputer's report, independent researchers demonstrated that these HTTP/2 memory flaws can be chained with a separate Linux kernel bug to break out of containers and achieve root privileges.

This report examines the mechanics behind all five disclosed vulnerabilities, the official patch versions available for mainline and commercial releases, and internet-wide exposure data. It is intended for infrastructure engineers, security personnel, and system administrators operating NGINX proxy and web workloads.

01Memory corruption and container escapes

The primary vulnerability designated CVE-2026-123007 is a flow-control flaw that corrupts memory inside an active NGINX worker process. The issue affects all versions from 1.31.8 down to 1.9.5, which first added HTTP/2 support in 2015. Researchers at Wiz achieved unauthenticated remote code execution on a test server delivering standard static files over HTTP/2 with TLS enabled.

Researchers at Xint demonstrated how an attacker can leverage this initial foothold to compromise the entire host system. By chaining CVE-2026-123007 with a separate vulnerability in the Linux kernel SCTP subsystem, they escaped an NGINX Docker container and gained root privileges on the underlying host. The demonstration showed that container sandboxing is insufficient when paired with exploitable network subsystems.

Security teams from Ikotas Labs, Metnir, and Rapid7 independently discovered the two HTTP/2 bugs alongside Xint and Wiz. Censys later reproduced the underlying memory corruption conditions for four of the five reported flaws within laboratory environments, though their test procedures stopped short of weaponizing remote code execution.

02Connection exhaustion and backend proxies

The second critical issue, tracked as CVE-2026-123633, is a use-after-free vulnerability that impacts NGINX when configured to receive HTTP/2 requests and reverse-proxy them to an upstream backend. It affects versions 1.19.7 through 1.31.8. When a worker process exhausts its available connection slots, it closes an active connection prematurely while an ongoing request still accesses the freed memory.

Wiz proved that the resulting memory corruption enables unauthenticated remote code execution against vulnerable reverse proxies. To F5 released security updates addressing two critical vulnerabilities dubbed nginx2root that allow unauthenticated attackers to execute arbitrary code remotely on servers running NGINX. As detailed in BleepingComputer's report, independent researchers demonstrated that these HTTP/2 memory flaws can be chained with a separate Linux kernel bug to break out of containers and achieve root privileges.

This report examines the mechanics behind all five disclosed vulnerabilities, the official patch versions available for mainline and commercial releases, and internet-wide exposure data. It is intended for infrastructure engineers, security personnel, and system administrators operating NGINX proxy and web workloads.

03Flow-control corruption and container escapes

The primary vulnerability designated CVE-2026-123007 is a flow-control flaw that corrupts memory inside an active NGINX worker process. The issue affects all versions from 1.31.8 down to 1.9.5, which first added HTTP/2 support in 2015. Researchers at Wiz achieved unauthenticated remote code execution on a test server delivering standard static files over HTTP/2 with TLS enabled.

Researchers at Xint demonstrated how an attacker can leverage this initial foothold to compromise the entire host system. By chaining CVE-2026-123007 with a separate vulnerability in the Linux kernel SCTP subsystem, they escaped an NGINX Docker container and gained root privileges on the underlying host. The demonstration showed that container sandboxing is insufficient when paired with exploitable network subsystems.

Security teams from Ikotas Labs, Metnir, and Rapid7 independently discovered the two HTTP/2 bugs alongside Xint and Wiz. Censys later reproduced the underlying memory corruption conditions for four of the five reported flaws within laboratory environments, though their test procedures stopped short of weaponizing remote code execution.

04Connection slot exhaustion in reverse proxies

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

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

The second critical issue, tracked as CVE-2026-123633, is a use-after-free vulnerability that impacts NGINX when configured to receive HTTP/2 requests and reverse-proxy them to an upstream backend. It affects versions 1.19.7 through 1.31.8. When a worker process exhausts its available connection slots, it closes an active connection prematurely while an ongoing request still accesses the freed memory.

Wiz proved that the resulting memory corruption enables unauthenticated remote code execution against vulnerable reverse proxies. To safeguard live production servers from opportunistic attacks, the research firm confirmed that it is withholding public proof-of-concept exploit scripts at this time. The attack path requires an accessible HTTP/2 listener that routes incoming traffic to internal backend destinations.

Exploitation relies on creating concurrent connection spikes that trigger the worker process resource cleanup routines during active stream processing. Once freed structures are repurposed, attackers can manipulate memory addresses to hijack the execution flow of the NGINX worker. This gives the adversary the identical privileges held by the web server process.

05Additional proxy flaws and loop triggers

Beyond the two nginx2root flaws, researchers identified three additional use-after-free issues that F5 resolved in the same maintenance release. CVE-2026-121810 affects HTTP/3 reverse proxying, while CVE-2026-123634 disrupts DNS resolution handling during subrequests. The third issue, CVE-2026-113425, exposes deployments that implement mail proxy authentication services.

F5 also patched five separate vulnerabilities across its software suite that were not part of the initial external research reports. The most critical among these uncredited issues is CVE-2026-118899, a high-severity denial-of-service flaw. It enables an unauthenticated attacker to force a worker process into an infinite execution loop while reading incoming request bodies over TLS 1.3.

These secondary vulnerabilities emphasize that modern web server risk extends across multiple transport and protocol stacks. The presence of overlapping use-after-free defects in HTTP/3 and DNS handling indicates that memory management during asynchronous proxy actions remains a common failure pattern. Administrators managing custom builds must verify every enabled protocol module.

06Official patches and temporary mitigations

F5 issued patched binaries across its supported open source and commercial product lines to eliminate all identified flaws. Open source administrators must update to stable version 1.30.7 or mainline release 1.31.9. Commercial installations running NGINX Plus must upgrade to versions 37.0.8.1 or 37.3.0.1 to obtain the corresponding fixes.

Release BranchVulnerable VersionsPatched Version
NGINX Mainline1.9.5 to 1.31.81.31.9
NGINX Stable1.9.5 to 1.30.61.30.7
NGINX PlusPrior to update37.0.8.1 or 37.3.0.1

For operational teams unable to deploy software updates immediately, disabling HTTP/2 on all exposed listening ports prevents exploitation of the primary remote code execution bugs. This temporary setting change shields the server from flow-control corruption and connection slot memory reuse.

Note: Disabling HTTP/2 only mitigates the two nginx2root flaws, leaving other proxy and TLS issues unaddressed until full upgrades take place.

07Internet scanner telemetry and exploit exposure

Security researcher Florian Roth analyzed the real-world attack surface, noting that while the flaws are technically worse than Node2Shell and Java2Shell, widespread compromise is not imminent. Commenting on X, Roth emphasized that these vulnerabilities demand non-default configurations and cautioned that version-only inventory audits present an inaccurate view of vulnerability.

Scanning a random sample of several hundred NGINX HTTPS endpoints via Shodan, Roth identified that 66 percent supported HTTP/2 negotiation. Although Xint observed that 98.9 percent of version-disclosing hosts ran affected releases, true exposure requires an open HTTP/2 listener, backend proxying for CVE-2026-123633, and an absence of vendor backported security patches.

Data published by Censys showed approximately 8.8 million internet-facing NGINX services met the criteria for CVE-2026-123007 exposure on November 19. The telemetry revealed that 511,000 servers had applied mitigations or updates, while an additional 104 million instances omitted version banners entirely, obscuring true patch compliance.

Frequently asked questions

What is the nginx2root vulnerability chain?

It combines an NGINX HTTP/2 remote code execution flaw with a Linux kernel SCTP bug to escape Docker containers and obtain root privileges.

Which NGINX versions are affected by the flaws?

CVE-2026-123007 impacts versions 1.9.5 through 1.31.8, while CVE-2026-123633 impacts reverse proxies on versions 1.19.7 through 1.31.8.

How can administrators mitigate the attack without updating?

Disabling HTTP/2 across listening interfaces prevents exploitation of the two nginx2root flaws, though full patching is required for secondary proxy bugs.

What patch versions resolve the vulnerabilities?

Deployments must upgrade to NGINX Open Source 1.30.7 stable, 1.31.9 mainline, or NGINX Plus releases 37.0.8.1 and 37.3.0.1.

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 →