Germany’s Federal Office for Information Security (BSI) is warning of five critical vulnerabilities in NGINX Open Source and NGINX Plus. Under the name “NGINX2Root,” researchers describe how attackers can execute code without authentication and potentially escalate their access to root privileges on the host system.
Administrators responsible for NGINX servers should take action promptly. On November 18, 2026, US-based F5, which has maintained the web server since acquiring NGINX Inc., published several security advisories addressing critical vulnerabilities in NGINX Open Source and NGINX Plus. Germany’s Federal Office for Information Security (BSI) followed with its own warning on November 19.
The vulnerabilities affect several components and processing paths in the widely deployed software: its HTTP/2 and HTTP/3 implementations, built-in DNS resolver, and mail proxy. Depending on the configuration, attackers could exploit these flaws to launch denial-of-service attacks, corrupt memory, or, in the worst-case scenario, execute malicious code remotely without prior authentication.
One Name, Five CVEs
The vulnerabilities are tracked as CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425. Security researchers at Xint have grouped the five NGINX vulnerabilities together with an additional Linux privilege escalation flaw under the name NGINX2Root. The name points to the potential attack chain: attackers first gain access through NGINX and then use the additional Linux vulnerability to escalate their privileges.
On its own, injected code initially runs with the permissions of the respective NGINX worker process. In typical installations, this process does not run as root. However, combining the NGINX vulnerabilities with the Linux flaw apparently allows attackers to overcome this limitation.
Severity ratings vary depending on the scoring standard used. Under CVSS 3.1, all five vulnerabilities receive a base score of 8.1 out of 10, placing them in the high-severity category. Under the newer CVSS 4.0 standard, they score 9.2, which qualifies as critical.
CVE-2026-123007 is particularly concerning. Xint has demonstrated that the vulnerability allows attackers to execute code with the privileges of the NGINX worker process without authentication. There is further cause for concern: cybersecurity firm Rapid7 has now published a functional proof-of-concept (PoC) exploit for the flaw.
Experience shows that once an exploit like this becomes publicly available, it is often only a matter of time before attackers incorporate it into their toolkits and begin automatically scanning the internet for vulnerable servers. Given NGINX’s enormous footprint, the number of potentially affected systems could be substantial. The software serves a significant share of websites worldwide and is also widely used in reverse proxies, load balancers, and ingress controllers.
What Administrators Should Do Now
Organizations running NGINX Open Source or NGINX Plus should review F5’s security advisories and install the available updates as soon as possible. Since exploitability depends on the specific configuration, administrators should also check which of the affected features (HTTP/2, HTTP/3, DNS resolver, or mail proxy) are actually enabled. Temporarily disabling modules that are not required can help reduce the attack surface.
Because NGINX2Root relies on an additional Linux privilege escalation vulnerability, administrators should also ensure that the underlying operating system is fully patched. Organizations running NGINX in containers should pay particular attention to potentially outdated images, which may also need to be rebuilt.
(Editorial Team)