Researchers have disclosed a critical remote code execution (RCE) vulnerability affecting NGINX HTTP/2 implementations, tracked as CVE-2026-123007 and disclosed as part of a set of flaws dubbed "nginx2root." The vulnerability has existed within NGINX codebases since September 2015 and allows unauthenticated attackers to execute code remotely on servers with HTTP/2 enabled.
Security researchers from Wiz, Rapid7, and Xint successfully demonstrated exploitation, with Xint reportedly achieving RCE against cloud-hosted systems exposed via public IP addresses across AWS, Azure, and GCP environments.
While code execution initially occurs in the context of an NGINX worker process, Xint reports that further privilege escalation is possible through a separate Linux kernel vulnerability, potentially leading to full system compromise. This kernel issue is unpatched and has not yet been confirmed in a vendor advisory.
F5 released fixes on 18 November 2026. The same updates address four further critical NGINX vulnerabilities, so patching should not be limited to systems running HTTP/2.
The vulnerability resides within NGINX's handling of HTTP/2 traffic and can permit remote attackers to trigger memory corruption conditions leading to arbitrary code execution. According to researchers, exploitation can occur by interacting with a reachable HTTP/2 service exposed by the target server.
Although initial code execution occurs under the security context of an NGINX worker process, Xint highlighted scenarios where attackers could leverage an additional, currently unpatched Linux kernel vulnerability to achieve root-level access, including from within Docker-based deployments. This element is researcher-reported and not vendor-confirmed.
The issue is particularly concerning because:
|
Version Range |
Status |
Fixed In |
|
1.31.0 - 1.31.8 (mainline) |
Vulnerable |
1.31.9 |
|
1.9.5 - 1.30.6 |
Vulnerable |
1.30.7 |
|
Version Range |
Status |
Fixed In |
|
37.1.0 - 37.2.0.1 |
Vulnerable |
37.3.0.1 |
|
37.0.0 - 37.0.7.1 |
Vulnerable |
37.0.8.1 |
|
R34 - R36 |
Vulnerable |
No fix available. Upgrade to a fixed 37.x release |
F5 also lists NGINX Instance Manager, F5 WAF for NGINX, NGINX App Protect WAF, F5 DoS for NGINX, NGINX App Protect DoS, NGINX Gateway Fabric and NGINX Ingress Controller as affected. Fixed versions for these products are listed in F5 advisory K000163926. Linux distributions and third-party products that bundle NGINX publish their own fixed versions.
Several factors increase the likelihood of exploitation:
Successful exploitation may result in:
No vendor-published indicators of compromise are available. CERT-EU and the reporting researchers recommend monitoring for:
F5 lists no mitigation other than upgrading. Where patching is not immediately possible, CERT-EU and the reporting researchers recommend the following:
openssl s_client -alpn h2 -connect <host>:443
If you are worried about any of the threats outlined in this bulletin or need help in determining what steps you should take to protect yourself from the most material threats facing your organisation, please contact your account manager, or alternatively get in touch to find out how you can protect your organisation.