A remote code execution (RCE) vulnerability, CVE-2026-123007, nicknamed "nginx2root," has been discovered in the NGINX open-source web server. The flaw has existed for over a decade and affects the server's HTTP/2 module. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary code with the permissions of an NGINX worker process. Researchers have demonstrated that this access can be escalated to full root privileges by chaining it with a local privilege escalation (LPE) vulnerability in the Linux kernel. The vulnerability impacts a vast range of NGINX versions, from 1.9.5 to 1.31.8. F5, the maintainer of NGINX, has released patches, and administrators are urged to update their servers, though exploitation is reportedly complex.
CVE-2026-123007 is a vulnerability in the way NGINX's HTTP/2 implementation handles certain traffic. While the exact technical nature of the flaw (e.g., buffer overflow, use-after-free) was not detailed in the source articles, it allows an attacker to achieve remote code execution.
http2 parameter on the listen directive).www-data or nginx).The vulnerability has a very wide-ranging impact due to its presence in the codebase for over ten years.
Given that NGINX is one of the most popular web servers in the world and HTTP/2 is commonly enabled for performance, the potential number of vulnerable systems is massive.
As of November 19, 2026, there are no known instances of CVE-2026-123007 being exploited in the wild. A public proof-of-concept (PoC) is available, but exploiting the vulnerability is considered difficult. One research team's demonstration required sending approximately 128 GB of HTTP/2 traffic over two minutes, which may limit its use to well-resourced attackers. The vulnerability has not yet been added to CISA's Known Exploited Vulnerabilities (KEV) catalog.
A successful exploit could lead to a complete compromise of the web server. Even without privilege escalation, an attacker with code execution as the nginx user can often read sensitive configuration files, access website data, or use the server as a pivot point to attack backend systems. If chained with a kernel exploit, the attacker gains full control over the host operating system, allowing them to install rootkits, exfiltrate all data, and maintain persistent access. The widespread deployment of NGINX makes this a high-impact vulnerability, even if the exploitation complexity currently limits its immediate threat.
The following patterns may help identify vulnerable systems or exploitation attempts:
network_traffic_patternlog_sourceprocess_namenginx worker processes/bin/sh) or making outbound network connections is a strong indicator of compromise.service_namenginx -v or check package manager details.D3-NTA: Network Traffic Analysis to identify the large, anomalous traffic flows characteristic of the known exploit PoC.apt update && apt upgrade, yum update).listen directives. This will cause clients to fall back to HTTP/1.1 and will mitigate the vulnerability, but may have a minor performance impact.# Vulnerable configuration
# listen 443 ssl http2;
# Mitigated configuration (workaround)
listen 443 ssl;
Upgrading to a patched version of NGINX is the most effective and recommended mitigation.
Disabling the HTTP/2 module serves as a temporary workaround if immediate patching is not possible.
Regularly scanning for vulnerable NGINX versions helps organizations identify their exposure.
NGINX version 1.9.5 is released, introducing the code that contains the vulnerability.
The 'nginx2root' vulnerability (CVE-2026-123007) is publicly disclosed.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.