Multiple Vulnerabilities in NGINX Could Allow for Remote Code Execution
MS-ISAC ADVISORY NUMBER:
2026-136DATE(S) ISSUED:
11/19/2026OVERVIEW:
Multiple vulnerabilities have been discovered in NGINX, the most severe of which could allow for remote code execution. NGINX is software used for web serving, reverse proxying, caching, and load balancing. Successful exploitation of the most severe of these vulnerabilities could result in remote code execution. Depending on the privileges associated with the account, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Accounts configured to have fewer user rights on the system could be less impacted than those that operate with administrative user rights.
THREAT INTELLIGENCE:
There are no reports of these vulnerabilities being exploited in the wild as of November 18, 2026. The five vulnerabilities have been collectively named “NGINX2Root.” The researchers who reported them state that each could allow code execution as the NGINX worker process. Rapid7 has demonstrated unauthenticated remote code execution for CVE-2026-123007 with a proof-of-concept, and Wiz has also confirmed code execution.
Code execution is possible where ASLR (address-space layout randomization), a memory protection feature, is disabled or can be bypassed. Rapid7’s proof-of-concept also requires sending a very large volume of network traffic to the target, which may limit exploitation in some environments. The researchers also report chaining these vulnerabilities with a separate Linux kernel flaw, unpatched at the time of disclosure, to gain root privileges on the host in tests, including from NGINX running in a container.
SYSTEMS AFFECTED:
- NGINX Open Source:
- Versions 0.5.33 through 1.30.6 and 1.31.0 through 1.31.8 (mail proxy, CVE-2026-113425)
- Versions 0.6.18 through 1.30.6 and 1.31.0 through 1.31.8 (resolver, CVE-2026-123634)
- Versions 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 (HTTP/2 flow control, CVE-2026-123007)
- Versions 1.19.7 through 1.30.6 and 1.31.0 through 1.31.8 (HTTP/2, CVE-2026-123633)
- Versions 1.25.0 through 1.30.6 and 1.31.0 through 1.31.8 (HTTP/3, CVE-2026-121810)
- NGINX Plus:
- 37.0.0 through 37.0.7.1 and 37.1.0 through 37.2.0.1 (CVE-2026-123007, CVE-2026-121810, CVE-2026-123634)
- 37.0.0 through 37.0.6.1 and 37.1.0 through 37.1.1 (CVE-2026-123633)
- 37.0.0 through 37.0.7 and 37.1.0 through 37.2.0 (CVE-2026-113425)
- R34 through R36 (no fixed R-series release is listed; upgrade to a fixed 37.x release)
- Other F5 products that bundle affected NGINX components:
- NGINX Ingress Controller: LTS 2026-lts-r1 through 2026-lts-r10 (fixed in 2026-lts-r11); 5.0.0 through 5.7.1 (fixed in 5.8.0); 4.0.0 through 4.0.1 and 3.7.1 through 3.7.2 (no fix listed)
- NGINX Gateway Fabric: 2.0.0 through 2.8.1 (fixed in 2.9.0); 1.5.0 through 1.6.2 (no fix listed)
- NGINX Instance Manager: 2.19.0 through 2.24.1 (fixed in 2.25.0)
- F5 WAF for NGINX: 5.9.0 through 5.16.1 (fixed in 5.16.2 and 5.14.4)
- NGINX App Protect WAF: 5.4.0 through 5.8.0 and 4.12.0 through 4.16.0 (no fix listed)
- F5 DoS for NGINX: 4.8.0 through 4.12.0 (fixed in 4.13.0)
- NGINX App Protect DoS: 4.5.0 through 4.7.0 (no fix listed)
RISK:
Government:
Businesses:
Home Users:
TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in NGINX, the most severe of which could allow for remote code execution. Details of these vulnerabilities are as follows:
Tactic: Initial Access (TA0001):
Technique: Exploit Public-Facing Application (T1190):
- Memory corruption in HTTP/2 flow control (CVE-2026-123007)
- Use-after-free in mail proxy module (CVE-2026-113425)
- Use-after-free in HTTP/3 (CVE-2026-121810)
- Use-after-free in HTTP/2 (CVE-2026-123633)
- Use-after-free in resolver (CVE-2026-123634)
Exposure depends on configuration:
- CVE-2026-123007: HTTP/2 enabled
- CVE-2026-123633: HTTP/2 enabled for client connections, requests proxied to a backend, and a worker process running low on worker connections
- CVE-2026-121810: HTTP/3 enabled
- CVE-2026-123634: NGINX configured as a proxy with variables in the proxied server name, and an SSI or mirror directive sending a subrequest to a location that resolves the same server name
- CVE-2026-113425: NGINX configured as a mail proxy server
Successful exploitation of the most severe of these vulnerabilities could result in remote code execution. Depending on the privileges associated with the account, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Accounts configured to have fewer user rights on the system could be less impacted than those that operate with administrative user rights.
RECOMMENDATIONS:
We recommend the following actions be taken:
- Apply appropriate updates provided by NGINX to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
- Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
- Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
- Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
- Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise's policy for remediation scope and prioritization.
- Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
- Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
- Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
- Safeguard 12.8: Establish and Maintain Dedicated Computing Resources for All Administrative Work: Establish and maintain dedicated computing resources, either physically or logically separated, for all administrative tasks or tasks requiring administrative access. The computing resources should be segmented from the enterprise's primary network and not be allowed internet access.
