Skip to content

NGINX2Root: critical NGINX vulnerabilities allow unauthenticated remote code execution (CVE-2026-123007 and four others)

F5 has fixed five critical memory-safety vulnerabilities in NGINX Open Source and NGINX Plus ("NGINX2Root"), the most serious in the HTTP/2 module, which can let an unauthenticated remote attacker crash NGINX worker processes and, under certain conditions, execute code. Update NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), or NGINX Plus to a fixed 37.x release; if you cannot update yet, disable HTTP/2 as a temporary workaround.

Critical External vulnerability announcement Patch available Published
Conflicting information

Some details in this advisory could not yet be fully verified against official sources, and available reports disagree. We will update it as official information becomes available.

Action required

If you run your own NGINX servers (including NGINX bundled in reverse proxies, load balancers, ingress controllers, container images or hosting control panels), update NGINX Open Source to 1.30.7 or 1.31.9 (or your distribution's patched package), or NGINX Plus to a fixed 37.x release. If you cannot update immediately, disable HTTP/2 until you can.

Affected software

SoftwareAffected versionsFixed versions
NGINX Open Source, NGINX Plus
F5 / NGINX
NGINX Open Source 1.9.5 – 1.31.8 (CVE-2026-123007, HTTP/2)
NGINX Open Source 1.19.7 – 1.31.8 (CVE-2026-123633, HTTP/2)
NGINX Open Source 0.6.18 – 1.31.8 (CVE-2026-123634, resolver)
NGINX Open Source 1.25.0 – 1.31.8 (CVE-2026-121810, HTTP/3)
NGINX Open Source 0.5.33 – 1.31.8 (CVE-2026-113425, mail proxy)
NGINX Plus R33 – R36 and 37.x before the fixed releases (see F5 K000163926)
NGINX Open Source 1.30.7 (stable)
NGINX Open Source 1.31.9 (mainline)

Overview

On 18 November 2026, F5 released NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), fixing ten security vulnerabilities. Five of them — nicknamed "NGINX2Root" by the researchers — are memory-safety bugs that F5, as the CVE Numbering Authority, rates 9.2 Critical (CVSS v4.0) and 8.1 High (CVSS v3.1). They were found independently by Wiz Research, Xint, Rapid7, Ikotas Labs and Metnir. NVD has not yet published its own assessment.

Affected and fixed versions (NGINX Open Source)

CVE Component Bug type You are exposed when Vulnerable Fixed
CVE-2026-123007 HTTP/2 (ngx_http_v2_module) Memory corruption in HTTP/2 flow control NGINX accepts HTTP/2 from clients 1.9.5 – 1.31.8 1.30.7, 1.31.9
CVE-2026-123633 HTTP/2 Use-after-free HTTP/2 is enabled and NGINX proxies to an upstream while a worker runs short of connections 1.19.7 – 1.31.8 1.30.7, 1.31.9
CVE-2026-123634 Resolver Use-after-free Upstream names are resolved at request time (variable in proxy_pass) and a subrequest (e.g. mirror, SSI) resolves the same name 0.6.18 – 1.31.8 1.30.7, 1.31.9
CVE-2026-121810 HTTP/3 / QUIC Use-after-free QUIC/HTTP/3 listeners are enabled 1.25.0 – 1.31.8 1.30.7, 1.31.9
CVE-2026-113425 Mail proxy (ngx_mail_proxy_module) Use-after-free Mail proxy listeners are in use 0.5.33 – 1.31.8 1.30.7, 1.31.9

Version ranges are taken from the official nginx.org security advisories page. Some third-party write-ups list different lower bounds for CVE-2026-123634 and CVE-2026-113425; the fixed versions are the same everywhere.

The same release also fixes five further issues that nginx.org rates lower: CVE-2026-118899 (infinite loop while reading a request body over TLS 1.3 — rated major), CVE-2026-120967 (SNI bypass with client-certificate validation in stream — medium), CVE-2026-125283 (buffer overflow with alias and try_files — minor), CVE-2026-123640 (insufficient validation in stream ssl_preread — minor) and CVE-2026-120993 (NULL pointer dereference with PROXY protocol v2 — minor, mainline 1.31.4–1.31.8 only).

NGINX Plus and other F5 products

According to F5's advisory as reported by researchers, CVE-2026-123007 is fixed in NGINX Plus 37.0.8.1 and 37.3.0.1, and CVE-2026-123633 in 37.0.7.1 and 37.2.0.1. R33–R36 reportedly receive no patch, so customers on those releases need to move to a fixed 37.x release. Other F5 products that bundle NGINX are covered in F5 article K000163926.

Technical impact

An unauthenticated remote attacker can send crafted traffic that crashes NGINX worker processes (denial of service) or corrupts memory. Remote code execution is possible when ASLR is disabled or can be bypassed, and runs with the privileges of the NGINX worker process. F5 states this is a data-plane issue and the control plane is not exposed. Xint reported chaining the flaws with a separate, still-unpatched Linux kernel SCTP use-after-free to gain root on the host.

Exploitation status

  • Rapid7 published a proof-of-concept for CVE-2026-123007 on disclosure day. It targets a freshly started lab container and needs a very large volume of HTTP/2 traffic over one connection; other approaches are not ruled out.
  • CERT-FR reports it is aware of a public proof-of-concept.
  • As of 19 November 2026 the vulnerabilities are not listed in the CISA Known Exploited Vulnerabilities catalogue and no in-the-wild exploitation has been reported.

Recommended actions

  1. Update NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), or install your distribution's or platform's patched package. Distribution packages may lag the upstream release.
  2. NGINX Plus: upgrade to a fixed 37.x release per F5 K000163926.
  3. Temporary workarounds if you cannot patch yet:
    • CVE-2026-123007 / CVE-2026-123633: disable HTTP/2 (http2 off; on 1.25.1+, and remove the legacy http2 parameter from listen lines).
    • CVE-2026-121810: remove quic from all listen directives.
    • CVE-2026-113425: bind mail proxy listeners to localhost or firewall them.
    • CVE-2026-123634: use fixed upstream groups instead of variable proxy_pass targets and disable mirror where not needed.
  4. Find the hidden NGINX: reverse proxies, load balancers, Kubernetes ingress controllers, container base images and hosting control panels often ship their own NGINX.

Workarounds only block the known attack paths — updating is the actual fix.

Timeline

  • 21 Oct 2026 — F5 notified about CVE-2026-123633.
  • 10 Nov 2026 — F5 shares a patch for CVE-2026-123633 with researchers for review.
  • 16 Nov 2026 — Wiz reports a second HTTP/2 flaw; F5 confirms on 17 Nov it matches the already-reported CVE-2026-123007.
  • 18 Nov 2026 — F5 security release (NGINX 1.30.7 / 1.31.9) and coordinated public disclosure.

References

Technical impact

A remote, unauthenticated attacker can send crafted traffic that crashes NGINX worker processes (denial of service) or corrupts their memory. Remote code execution is possible when ASLR is disabled or can be bypassed; the code runs with the privileges of the NGINX worker process, which is normally an unprivileged account. F5 states the control plane is not exposed and this is a data-plane issue. Researchers at Xint reported chaining these flaws with a separate, still-unpatched Linux kernel SCTP use-after-free to obtain root on the host. Exposure depends on configuration: HTTP/2 (CVE-2026-123007, CVE-2026-123633), HTTP/3/QUIC (CVE-2026-121810), runtime DNS resolution of upstream names with subrequests (CVE-2026-123634) and the mail proxy module (CVE-2026-113425).

Recommended mitigation

  1. Update NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), or install your distribution's or platform's patched package. Distribution packages may lag the upstream release — check your vendor's security tracker.
  2. NGINX Plus: upgrade to a fixed 37.x release as listed in F5 article K000163926. R33–R36 reportedly receive no fix; move to a fixed 37.x release.
  3. If you cannot patch immediately, apply the temporary workarounds:
    • CVE-2026-123007 / CVE-2026-123633: disable HTTP/2 (http2 off; on 1.25.1 and later, and remove the legacy http2 parameter from listen directives).
    • CVE-2026-121810: remove the quic parameter from all listen directives.
    • CVE-2026-113425: bind mail proxy listeners to localhost or restrict access with a firewall.
    • CVE-2026-123634: use fixed upstream groups instead of variable proxy_pass targets and turn off mirror where it is not needed.
  4. Inventory where NGINX runs indirectly (reverse proxies, load balancers, Kubernetes ingress, container base images, hosting panels) — these are easy to miss. Workarounds only block the known attack paths; updating is the actual fix.

References