Technology & security · · 8 min read ·

NGINX2Root: What website owners should have checked now

NGINX2Root refers to five vulnerabilities in the NGINX web server software. NGINX may also be used in front of WordPress or Apache. Current WordPress plugins do not fix these server issues. Ask your hosting provider to check whether your environment is affected and whether the necessary fixes are already running. Research status: 19 November 2026, around 16 o’clock Central European Time.

NGINX2Root: Check security updates for NGINX and Plesk
NGINX2Root: Check security updates for NGINX and Plesk

What happened?

On 18 November 2026, F5 confirmed five NGINX vulnerabilities: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. The F5 records rate each one at 8,1 under CVSS v3.1 (“high”) and 9,2 under CVSS v4.0 (“critical”). CVSS describes the technical severity of a vulnerability.

The flaws affect the HTTP/2 and HTTP/3 transfer protocols, certain name resolution configurations and the NGINX mail proxy. Depending on the configuration, they may corrupt memory, crash worker processes or enable remote code execution, known as RCE. In some cases, the ASLR memory protection must be absent or bypassed.

Code execution in an NGINX worker process does not automatically mean full administrator access to the server. To gain this root access to the host, the published laboratory chain also used a separate flaw in the Linux kernel’s SCTP network protocol.

How dangerous is NGINX2Root in practice?

For CVE-2026-123007, Rapid7 published a PoC, a program that demonstrates the vulnerability, and demonstrated code execution in a laboratory. Wiz and the Censys repository reviewed also document laboratory RCE. These results justify action, but they do not prove that your website has been breached. An attempted attack alone likewise does not prove successful access.

The picture regarding exploitation outside test environments remains incomplete: on 19 November, WASOC reported that it had been alerted to exploitation, but did not provide publicly verifiable technical evidence of incidents. On 18 November, CERT-EU and Censys were still reporting no known exploitation. This does not show either that all attacks are absent or that there is a widespread wave of attacks.

The research found no entry for the five CVEs in the reviewed official mirror of the CISA KEV catalogue dated 18 November. The absence of an entry in this catalogue of known exploited vulnerabilities is not proof that attacks are not taking place.

Which NGINX and Plesk versions are fixed?

The following fixed versions are documented for the five vulnerabilities described. They are not a general security guarantee.

  • NGINX Open Source directly from the project: 1.30.7 or later in the Stable branch, or 1.31.9 or later in the Mainline branch.
  • NGINX Plus: 37.0.8.1 or 37.3.0.1 for the entire group. The earlier versions 37.0.7.1 and 37.2.0.1 fix only CVE-2026-123633 within this group.
  • Plesk for Linux: 18.0.82 Update 4 or 18.0.81 Update 9. The changelog dated 19 November documents NGINX base 1.30.7 for the website web server sw-nginx and the management interface web server sw-cp-server.

The older Plesk security notice still leaves the release date open; the newer changelog already documents the updates. This does not prove that the hosting provider has installed them. Both Plesk components must be checked separately.

Linux distributors can backport fixes to older versions. Such backports retain an older visible NGINX version number. What matters is the full package version, the package source and the corresponding security notice from the vendor.

After replacing a program, reloading the configuration is not enough. The administrator must fully complete an appropriate service restart or a supported binary upgrade and terminate old vulnerable processes. With cPanel, the designated cPanel service procedure must be used.

How can I check whether my website is affected?

In WordPress, the visible server environment is shown under “Tools → Site Health → Info → Server”. This report does not check the complete patch status of upstream systems. Seeing “Apache” also does not rule out an NGINX proxy, an intermediary server, running in front of it.

In Plesk, depending on your permissions, you can find version details under “Tools & Settings → About Plesk” or “Plesk Updates”. The domain settings under “Apache & nginx Settings” show neither all global settings nor the patch status of the panel web server. Read the available information; do not change security directives based on suspicion alone.

cPanel may show version details under “Server Information” if the hosting provider has enabled this function. This is not complete evidence of the NGINX patch status. NGINX may operate there as the ea-nginx package in front of Apache.

With Shared Hosting, you need confirmation from the provider for your specific environment. A static website can also be located behind an affected web server. A page that loads normally does not provide an all-clear. Administrative server checks should be performed by authorised administrators.

What should I write to my hosting provider?

Copy the following enquiry and replace the placeholders:

Hello, please check CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425 for [DOMAIN], customer number [NUMMER]. Is NGINX used for our website, upstream systems, the management interface or as a mail proxy? For each component, please confirm the full package/build version, the vendor and the security notice for the fix. For Plesk, we need separate information on sw-nginx and sw-cp-server, as well as the Plesk version including the update number; for cPanel, please also provide information on ea-nginx.

Are the fixed programs active and have all old vulnerable processes been terminated? If the update is still pending: which interim measures apply to which CVEs, which risks remain and when will the update be carried out? Please check HTTP/2, HTTP/3/QUIC, resolver with SSI/mirror, and the mail proxy separately.

If Cloudflare is used upstream: is the origin server also protected against bypass through direct IP addresses, alternative names and ports? Are there specific indications of a compromise, meaning successful unauthorised access, or has this not yet been conclusively checked? Please reply in writing and with reference to our hosting environment. Thank you.

What if the update cannot be installed immediately?

Interim measures are the administrator’s responsibility. Red Hat and CIRCL describe disabling protocols: disabling HTTP/2 at all affected endpoints blocks the two HTTP/2 attack paths. Disabling HTTP/3 and removing QUIC endpoints addresses the HTTP/3 flaw. The other vulnerabilities remain; changes may affect services.

For the resolver, which provides name resolution, the combination of variable proxy destination names and SSI or mirror subrequests for the same name must be avoided, if necessary by using fixed destination servers. Disabling only mirror is not enough if SSI leaves the flaw reachable. The NGINX mail proxy can be disabled or restricted to trusted networks. A network restriction only reduces the potential group of attackers and does not fix an HTTP or resolver vulnerability.

Cloudflare describes conditional protection through its HTTP proxy: client connections over HTTP/2 and HTTP/3 terminate there. The origin, your original server, must be reachable exclusively through it and protected against direct bypass. DNS-only, Spectrum-TCP/UDP and mail proxies are excluded; the resolver path remains dependent on the configuration. The Cloudflare notice reviewed does not mention a published Managed WAF rule, meaning a corresponding managed firewall rule. The update is still required.

If neither the update nor effective restrictions are possible, the hosting provider should consider restricting access or temporarily disabling affected services. This causes outages and does not replace a fix. A WordPress maintenance page alone does not disable the upstream NGINX web server.

Frequently asked questions about NGINX2Root

My WordPress plugins are up to date – is that enough?

Plugin updates do not fix flaws in the upstream NGINX web server. Ask for separate confirmation of the package version currently running.

Am I safe with Cloudflare?

This depends on the proxy service, its configuration and an origin server that is protected against bypass. Cloudflare does not replace the required NGINX update.

Is a static website affected?

It may be affected. What matters is the NGINX web server delivering the site or running upstream. Code execution was also demonstrated in a laboratory with static files.

Does NGINX2Root automatically mean root access?

No. Code execution in the NGINX worker does not automatically provide root access to the host. The published laboratory chain also required a separate Linux SCTP vulnerability.

Has my website already been hacked?

This cannot be inferred from an affected version, an attempted attack or laboratory evidence. Ask the hosting provider to check for specific indications of compromise.

Is the displayed NGINX version number enough?

No. Backports can retain older version numbers. You need the full package/build version, the corresponding vendor security notice and a check of the programs currently running.

Website subscription — from €79/month

Custom web design, German hosting, maintenance and personal support in one monthly package.

Book a free consultation

← All guide articles