NGINX2Root: Five Critical NGINX Flaws Expose Web Servers to Remote Code Execution

Copy of Template Design OX Blog (2)
Share

Unauthenticated attackers can run code on NGINX servers through HTTP/2, HTTP/3, proxying and mail proxy setups. Administrators are urged to upgrade to 1.31.9 immediately.

On November 18, 2026, F5 released fixes for five NGINX vulnerabilities, which researchers have named nginx2root. Xint’s research team found all five, and each one leads to remote code execution on its own, but under different configurations. Wiz Research, Ikotas Labs, Metnir and Rapid7 also independently reported issues to F5. The most serious one, CVE‑2026‑123007, has been present since NGINX introduced HTTP/2 in 2015. A working exploit for CVE‑2026‑123007 by Rapid7 is already public, although no exploitation in the wild has been confirmed.

What is NGINX?

NGINX is an open-source web server, reverse proxy and load balancer, and one of the most widely deployed web servers in the world. F5 also offers a commercial edition, NGINX Plus. It sits in front of many web applications, APIs and Kubernetes ingress setups.

Affected versions

Each of the five vulnerabilities is an independent attack path, and they don’t need to be chained together.

PackageCVEComponentVersionsFixed VersionsEcosystem
nginxCVE‑2026‑123007HTTP/2 flow control1.9.5 – 1.31.81.30.7 / 1.31.9NGINX Open Source
nginxCVE‑2026‑123634DNS resolver + mirror1.13.4 – 1.31.81.31.9NGINX Open Source
nginxCVE‑2026‑123633HTTP/2 + upstream proxy1.19.7 – 1.31.81.30.7 / 1.31.9NGINX Open Source
nginxCVE‑2026‑121810HTTP/3 + upstream proxy1.25.0 – 1.31.81.31.9NGINX Open Source
nginxCVE‑2026‑113425Mail proxy (auth_http)0.5.15 – 1.31.81.31.9NGINX Open Source
NGINX PlusCVE‑2026‑123007HTTP/2 flow control37.0.0 – 37.0.7.1, 37.1.0 – 37.2.0.137.0.8.1 / 37.3.0.1NGINX Plus
NGINX PlusCVE‑2026‑123633HTTP/2 + upstream proxy37.0.0 – 37.0.6.1, 37.1.0 – 37.2.037.0.7.1 / 37.2.0.1NGINX Plus
NGINX PlusBoth above—R34 – R36No fix – upgrade to 37.xNGINX Plus

Recommendations

  • Upgrade now. Update to 1.31.9, or to your Linux distribution’s backported package. Distros may backport fixes without changing the version that nginx -v reports, so check the full package version against the distro’s advisory.
  • Restart after patching. A configuration reload alone does not replace the running executable.
  • Mitigate if you can’t patch yet. Disabling HTTP/2 blocks CVE‑2026‑123007 and CVE‑2026‑123633, but not the other three. For the others, disable HTTP/3, avoid resolving upstream addresses dynamically during the request phase, and stop exposing the mail proxy publicly or restrict access to it.