NGINX 'nginx2root' Flaw CVE-2026-123007 Enables RCE

Decade-Old 'nginx2root' Flaw (CVE-2026-123007) Allows RCE on NGINX Servers

HIGH
November 19, 2026
5m read
VulnerabilityPatch Management

Related Entities

Organizations

Products & Tech

NGINX NGINX PlusDockerUbuntuDebian

CVE Identifiers

Full Report

Executive Summary

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.


Vulnerability Details

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.

  • Attack Vector: The attack is performed remotely and requires no authentication. The attacker sends a large volume of specially crafted HTTP/2 traffic to a vulnerable server.
  • Prerequisites: The target NGINX server must have the HTTP/2 module enabled (http2 parameter on the listen directive).
  • Initial Impact: Successful exploitation grants the attacker code execution capabilities within the context of the NGINX worker process. These processes typically run as a low-privilege user (e.g., www-data or nginx).
  • Privilege Escalation: Although the initial execution is unprivileged, researchers showed it can be chained with a separate kernel LPE to gain full root access, even within a Docker container. This makes the vulnerability significantly more severe.

Affected Systems

The vulnerability has a very wide-ranging impact due to its presence in the codebase for over ten years.

  • NGINX Open Source: Versions 1.9.5 (released September 22, 2015) through 1.31.8 are vulnerable.
  • NGINX Plus: Releases R34 through R36, and 37.x releases before the patched builds are affected.
  • Operating System Packages: Linux distributions that package NGINX, such as Ubuntu and Debian, were reportedly still shipping vulnerable versions at the time of disclosure. Administrators must check for updates from their respective package managers.

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.


Exploitation Status

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.


Impact Assessment

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.


Cyber Observables — Hunting Hints

The following patterns may help identify vulnerable systems or exploitation attempts:

Type
network_traffic_pattern
Value
Unusually large volume of HTTP/2 traffic from a single source IP
Description
The reported exploit requires sending ~128 GB of traffic. Such a large, sustained data flow to an NGINX server is highly anomalous and should be investigated.
Type
log_source
Value
NGINX access and error logs
Description
Look for a high rate of connections or unusual error messages related to the HTTP/2 module that coincide with network traffic spikes.
Type
process_name
Value
Anomalous child processes of nginx worker processes
Description
An NGINX worker process spawning a shell (/bin/sh) or making outbound network connections is a strong indicator of compromise.
Type
service_name
Value
NGINX version check
Description
Use asset inventory or vulnerability scanners to identify all NGINX instances running vulnerable versions (1.9.5 - 1.31.8).

Detection Methods

  • Version Scanning: The most reliable detection method is to check the version of all running NGINX instances. Use commands like nginx -v or check package manager details.
  • Network Traffic Analysis: Monitor for abnormally large and sustained inbound traffic flows over TCP port 443 to NGINX servers. Set up alerts for traffic volumes exceeding a high threshold from a single client over a short period.
  • Endpoint Detection and Response (EDR): Monitor NGINX worker processes for anomalous behavior, such as file creation in unexpected directories, spawning of shells, or outbound network connections.
  • D3FEND: Employ D3-NTA: Network Traffic Analysis to identify the large, anomalous traffic flows characteristic of the known exploit PoC.

Remediation Steps

  1. Upgrade NGINX: The primary remediation is to upgrade to a patched version. F5 has released fixes in NGINX Open Source 1.31.9 and 1.30.7. Users of NGINX Plus should consult F5 for the appropriate patched release. Users of distribution-packaged NGINX must update via their system's package manager (e.g., apt update && apt upgrade, yum update).
  2. Disable HTTP/2 (Workaround): If patching is not immediately possible, a temporary workaround is to disable HTTP/2 support on your server's 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;
    
  3. Kernel Patching: To prevent the full 'nginx2root' chain, ensure your servers are running a Linux kernel patched against known local privilege escalation vulnerabilities.

Timeline of Events

1
September 22, 2015
NGINX version 1.9.5 is released, introducing the code that contains the vulnerability.
2
November 19, 2026
The 'nginx2root' vulnerability (CVE-2026-123007) is publicly disclosed.
3
November 19, 2026
This article was published

MITRE ATT&CK Mitigations

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.

Timeline of Events

1
September 22, 2015

NGINX version 1.9.5 is released, introducing the code that contains the vulnerability.

2
November 19, 2026

The 'nginx2root' vulnerability (CVE-2026-123007) is publicly disclosed.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

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.

Tags

NGINXCVE-2026-123007nginx2rootRCEVulnerabilityHTTP/2F5Patch Management

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.