NGINX Fixes Five Critical Vulnerabilities Allowing Remote Code Execution
F5 has released patches for five critical NGINX vulnerabilities, dubbed NGINX2Root, that could allow unauthenticated remote attackers to execute arbitrary code on affected web servers.

By Elena Rostova, Cybersecurity
3 min read
F5 has announced patches for five critical vulnerabilities affecting NGINX, collectively dubbed "NGINX2Root." These flaws could allow remote, unauthenticated attackers to execute arbitrary code on vulnerable servers, posing a significant risk to web infrastructure.
The vulnerabilities, tracked as CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, and CVE-2026-123634, carry CVSS scores up to 9.2, indicating their critical severity. NGINX is a widely deployed open-source web server, reverse proxy, and load balancer, making these security issues particularly impactful.
Details of the NGINX2Root Vulnerabilities:
CVE-2026-113425 (Mail Proxy Use-After-Free): Affects NGINX instances configured as mail proxy servers. Exploitation is possible via specially crafted mail sessions, leading to potential remote code execution.
CVE-2026-121810 (HTTP/3 Use-After-Free): Can be exploited on servers that use HTTP/3 (QUIC) to trigger a use-after-free condition in the NGINX worker process, potentially leading to RCE.
CVE-2026-123007 (HTTP/2 Memory Corruption): A memory corruption vulnerability in the HTTP/2 flow control implementation. This is rated as major severity and could allow RCE on servers using HTTP/2.
CVE-2026-123633 (HTTP/2 Use-After-Free): Another use-after-free in HTTP/2 processing, also rated as medium severity.
CVE-2026-123634 (Resolver Use-After-Free): A use-after-free during response processing in the resolver module, rated as medium severity.
Affected Versions and Patches:
All NGINX versions from 1.9.5 up to 1.31.8 are affected by at least one of these vulnerabilities. The mail proxy vulnerability (CVE-2026-113425) affects versions 0.6.18 through 1.31.8.
F5 has released patched versions:
NGINX 1.31.9 (mainline)
NGINX 1.30.7 (stable)
Both releases address all five vulnerabilities. Users on older branches should upgrade immediately.
Why This Matters:
NGINX powers a significant portion of the world's web servers, load balancers, and reverse proxies. The NGINX2Root vulnerabilities are particularly dangerous because they can be exploited remotely without authentication on servers using common configurations like HTTP/2, HTTP/3, mail proxy, or DNS resolver functions. Proof-of-concept exploits are already public, increasing the urgency for patching.
System administrators should prioritise updating to 1.31.9 or 1.30.7 as soon as possible. If immediate upgrading is not feasible, consider mitigations such as disabling HTTP/2, HTTP/3, mail proxy, or resolver modules if they are not required, though upgrading remains the only complete fix.
Sources
- 1F5 Security Advisory: NGINX2Rootsecurityweek.com
- 2NGINX Official Security Advisoriesnginx.org