Executive Summary
On November 18, 2026, F5 disclosed CVE-2026-123007 — dubbed 'nginx2root' — a critical remote code execution vulnerability (CVSS 4.0: 9.2) present in NGINX's HTTP/2 implementation since version 1.9.5 released in September 2015. An unauthenticated attacker with network access to an HTTP/2-enabled NGINX port can execute arbitrary code at the privilege level of an NGINX worker process. Researchers at Wiz, Xint, and Rapid7 independently demonstrated successful exploitation across AWS, GCP, and Azure environments, including over public IP addresses. When chained with a separate Linux kernel SCTP vulnerability, attackers can escalate to root even from within Docker containers. Fixed versions 1.31.9 and 1.30.7 were released the same day; no active exploitation has been confirmed as of disclosure.
This vulnerability exposes a decade-long blind spot in one of the world's most widely deployed web servers. With public proof-of-concept code already available on GitHub and confirmed exploitation across all three major cloud providers, organizations running unpatched NGINX — including those behind CDNs — face imminent unauthenticated RCE risk that demands immediate patching, HTTP/2 disablement as an interim control, and network-layer lateral movement containment.
Why This Matters Now
Public PoC code for CVE-2026-123007 is already live on GitHub, and researchers have confirmed unauthenticated RCE against NGINX on AWS, GCP, and Azure over public IPs. With Ubuntu and Debian package fixes not yet shipped and NGINX Plus R34–R36 lacking a listed fix, millions of production servers remain exposed. The kernel SCTP chain enabling container escape to root dramatically raises the blast radius for cloud-hosted workloads.
Attack Path Analysis
An unauthenticated attacker exploiting CVE-2026-123007 sends crafted HTTP/2 frames to a reachable NGINX server, triggering an integer underflow that enables remote code execution as the NGINX worker process. From there, the attacker chains a secondary Linux kernel SCTP vulnerability to escalate to root, moves laterally within the host or container environment, establishes outbound command-and-control channels, and may exfiltrate data or deploy destructive payloads — all detectable through anomalous long-lived HTTP/2 connections, unexpected worker process spawns, and unusual outbound DNS or network activity.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
The attacker identifies a publicly reachable NGINX server with HTTP/2 enabled (confirmed via ALPN negotiation returning 'h2'). By sending approximately 128 GB of specially crafted HTTP/2 control frames over TLS, the attacker triggers CVE-2026-123007, an integer underflow in NGINX's HTTP/2 stack present since version 1.9.5. This yields remote code execution as the NGINX worker process without any authentication. The attack was validated on AWS, GCP, and Azure over public IP addresses. CNSF inline IPS (Suricata) with signatures covering the CVE-2026-123007 exploit pattern could detect and block malicious HTTP/2 frame sequences at the network boundary. Cloud Firewall (ACF) egress NAT and inbound policy enforcement could limit exposure of the HTTP/2 port to untrusted sources.
Related CVEs
CVE-2026-123007
CVSS 8.1An integer underflow vulnerability in NGINX's HTTP/2 implementation allows an unauthenticated remote attacker to execute arbitrary code with the privileges of an NGINX worker process on servers with HTTP/2 enabled, potentially leading to full host compromise when chained with a local privilege escalation.
Affected Products:
F5 / NGINX NGINX Open Source – 1.9.5 through 1.31.8, >= 1.9.5, < 1.30.7 (stable), >= 1.31.0, < 1.31.9 (mainline)
F5 / NGINX NGINX Plus – R34, R35, R36, 37.0.0 through 37.2.0.1
Exploit Status:
proof of conceptReferences:
https://nginx.org/en/security_advisories.htmlhttps://my.f5.com/manage/s/article/K000163926https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/https://www.wiz.io/blog/nginx-http2-rce-vulnerabilitieshttps://xint.io/blog/nginx2root-remote-code-executionhttps://www.circl.lu/pub/tr-105/https://github.com/sfewer-r7/CVE-2026-123007CVE-2026-123633
CVSS 8.1A memory exhaustion or corruption vulnerability in NGINX's HTTP/2 request proxying triggers when worker connections are nearly exhausted, allowing an unauthenticated remote attacker to potentially execute arbitrary code under the same ASLR bypass conditions as CVE-2026-123007.
Affected Products:
F5 / NGINX NGINX Open Source – 1.9.5 through 1.31.8
F5 / NGINX NGINX Plus – R34, R35, R36, 37.0.0 through 37.1.x
Exploit Status:
proof of conceptCVE-2026-123634
CVSS 8.1A vulnerability in NGINX's resolver when a proxied server name is built from variables and combined with a server-side include (SSI) or mirror subrequest to a location resolving the same name can allow code execution under conditions where ASLR is disabled or bypassed.
Affected Products:
F5 / NGINX NGINX Open Source – 1.9.5 through 1.31.8
F5 / NGINX NGINX Plus – R34, R35, R36, 37.0.0 through 37.2.0.1
Exploit Status:
proof of conceptCVE-2026-121810
CVSS 8.1A vulnerability in NGINX's HTTP/3 support can allow an unauthenticated remote attacker to execute arbitrary code when HTTP/3 is enabled, under conditions where ASLR is disabled or can be bypassed.
Affected Products:
F5 / NGINX NGINX Open Source – 1.9.5 through 1.31.8
F5 / NGINX NGINX Plus – R34, R35, R36, 37.0.0 through 37.2.0.1
Exploit Status:
proof of conceptCVE-2026-113425
CVSS 8.1A vulnerability in NGINX when used as a mail proxy can allow an unauthenticated remote attacker to execute arbitrary code when the mail proxy listener is exposed to untrusted networks, under conditions where ASLR is disabled or can be bypassed.
Affected Products:
F5 / NGINX NGINX Open Source – 1.9.5 through 1.31.8
F5 / NGINX NGINX Plus – R34, R35, R36, 37.0.0 through 37.2.0.1
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Exploitation for Client Execution
Exploitation for Privilege Escalation
Process Injection
Escape to Host
Application Layer Protocol: Web Protocols
Impair Defenses: Disable or Modify Tools
Network Service Discovery
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Timely Patching of Software Vulnerabilities
Control ID: Requirement 6.3.3
NYDFS 23 NYCRR 500 – Vulnerability Management and Access Control
Control ID: Section 500.7 — Access Privileges & Section 500.5 — Penetration Testing
DORA (EU 2022/2554) – ICT Risk Management and Vulnerability Remediation
Control ID: Article 9 — ICT Security Policies and Article 10 — ICT-Related Incident Management
NIS2 Directive (EU 2022/2555) – Patch Management, Network Security, and Incident Handling
Control ID: Article 21 — Cybersecurity Risk Management Measures
CISA Zero Trust Maturity Model 2.0 – Micro-Segmentation, Least Privilege Access, and Workload Isolation
Control ID: Network Pillar — Network Segmentation and Application Pillar — Application Security
ISO/IEC 27001:2022 – Vulnerability Management and Secure Configuration Baseline
Control ID: Annex A 8.8 — Management of Technical Vulnerabilities and A 8.25 — Secure Development Life Cycle
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
NGINX's CVE-2026-123007 RCE flaw directly exposes IT infrastructure running HTTP/2-enabled servers, enabling unauthenticated code execution, lateral movement, and exfiltration risks across unpatched cloud and on-premise deployments.
Financial Services
Unauthenticated RCE via NGINX HTTP/2 threatens payment and banking web services; PCI 4.0 and NIST.800-53 compliance gaps emerge if unpatched servers expose cardholder data to exfiltration or privilege escalation attacks.
Health Care / Life Sciences
NGINX-powered patient portals and clinical APIs face critical HIPAA.164.312 compliance violations if CVE-2026-123007 enables unauthenticated code execution, lateral movement, and PHI exfiltration across hybrid cloud environments.
Internet
Web-facing services and SaaS platforms built on NGINX face immediate RCE exposure; AWS, GCP, and Azure deployments confirmed vulnerable, with east-west lateral movement amplifying blast radius across multitenant cloud infrastructure.
Sources
- 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servershttps://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.htmlVerified
- NGINX Security Advisories - Official F5/NGINX Advisory Pagehttps://nginx.org/en/security_advisories.htmlVerified
- F5 Support Advisory K000163926 - NGINX Plus Vulnerability Detailshttps://my.f5.com/manage/s/article/K000163926Verified
- CIRCL Technical Report TR-105 - NGINX HTTP/2 RCE Response Guidancehttps://www.circl.lu/pub/tr-105/Verified
- Rapid7 Blog - CVE-2026-123007 Critical NGINX HTTP/2 Integer Underflow Leads to RCEhttps://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/Verified
- Wiz Research - NGINX HTTP/2 RCE Vulnerabilities Disclosurehttps://www.wiz.io/blog/nginx-http2-rce-vulnerabilitiesVerified
- Xint Research - nginx2root Remote Code Execution Technical Reporthttps://xint.io/blog/nginx2root-remote-code-executionVerified
- NGINX Open Source Changelog - Official Release Notes for 1.31.9 and 1.30.7https://nginx.org/en/CHANGESVerified
- Proof-of-Concept Code for CVE-2026-123007 by Rapid7 (sfewer-r7)https://github.com/sfewer-r7/CVE-2026-123007Verified
- Ubuntu Security CVE Status - CVE-2026-123007https://ubuntu.com/security/CVE-2026-123007Verified
- Debian Security Tracker - CVE-2026-123007https://security-tracker.debian.org/tracker/CVE-2026-123007Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant because CVE-2026-123007 enables unauthenticated remote code execution against publicly reachable NGINX servers, with a clear chain into privilege escalation, lateral movement, and outbound C2. By enforcing segmentation, restricting east-west flows, and controlling egress paths, CNSF would likely reduce the attacker's ability to move beyond the initially compromised workload and establish persistent external channels.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Inline IPS enforcement with signatures covering the CVE-2026-123007 HTTP/2 frame exploit pattern could detect and disrupt the malicious frame sequence before RCE is achieved, and inbound policy controls would likely reduce the reachability of the HTTP/2 service to untrusted external sources.
Control: Zero Trust Segmentation
Mitigation: Zero Trust Segmentation enforcing least-privilege service identity and namespace-scoped policies would likely constrain what the compromised NGINX worker process can access, reducing the blast radius of the exploit even if the kernel escalation itself is not directly prevented at the network layer.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely detect and block unauthorized internal flows originating from the compromised NGINX host or worker context, constraining the attacker's ability to reach internal services that are not explicitly permitted under segmentation policy.
Control: Multicloud Visibility & Control
Mitigation: Centralized multicloud traffic visibility would likely surface anomalous outbound connections and unusual DNS query patterns originating from the NGINX worker process, reducing the attacker's ability to maintain undetected C2 channels across the environment.
Control: Egress Security & Policy Enforcement
Mitigation: Egress policy enforcement with FQDN-based filtering would likely restrict outbound data transfers to unauthorized external destinations, constraining the attacker's ability to move sensitive material out of the environment through unapproved channels.
Because CNSF controls would likely have reduced lateral reachability, constrained egress paths, and surfaced anomalous activity earlier in the chain, the attacker's options at the impact stage would likely be limited to damage within the initially compromised workload rather than across the broader cloud environment or connected systems.
Impact at a Glance
Affected Business Functions
- Web Application Hosting and API Gateway Services
- Reverse Proxy and Load Balancing Infrastructure
- Mail Proxy and Email Routing Services
- CDN Origin Server and TLS Termination
Estimated downtime: 3 days
Estimated loss: N/A
No confirmed data exfiltration or breaches reported as of disclosure date. However, successful exploitation of CVE-2026-123007 or related CVEs would grant an attacker code execution as an NGINX worker process, exposing all data processed by that worker including TLS session keys, decrypted HTTPS request and response payloads, authentication tokens, session cookies, and proxied application data. When chained with the Linux kernel SCTP privilege escalation demonstrated in Xint research, full host-level compromise is achievable including access to all data at rest and in memory on the affected server, even within Docker container environments. Affected deployments span cloud providers including AWS, GCP, and Azure. All Linux distributions running unpatched NGINX versions 1.9.5 through 1.31.8 are at risk, including Ubuntu 16.04 through 26.10 and Debian bookworm, trixie, forky, and sid.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Inline IPS (Suricata) with signatures covering CVE-2026-123007 HTTP/2 integer underflow exploit patterns to detect and block malicious frame sequences before they reach unpatched NGINX instances, buying time for patch deployment across all affected versions (1.9.5–1.31.8 and NGINX Plus R34–R36).
- • Enforce Zero Trust Segmentation with least-privilege identity-based policy to restrict NGINX worker process network access to only required upstream services, preventing lateral movement and limiting the blast radius if a worker process is compromised via CVE-2026-123007.
- • Activate Egress Security and Policy Enforcement with FQDN-based outbound filtering on all hosts running NGINX to block unauthorized outbound connections indicative of C2 establishment or data exfiltration following successful code execution.
- • Use Multicloud Visibility and Control to baseline normal NGINX traffic patterns and alert on anomalies such as long-lived HTTP/2 connections with high inbound volume but low logged request counts, unexpected worker process child spawns, and unusual outbound DNS lookups as described in CIRCL's response guidance.
- • Apply Kubernetes Security (AKF) pod-level segmentation and namespace enforcement for all containerized NGINX deployments to contain the demonstrated container escape via the Linux kernel SCTP vulnerability, and block SCTP kernel module loading on hosts that do not require it via /etc/modprobe.d/ configuration.



