nginx vulnerabilities “NGINX2Root”
Our servers are protected for now – HTTP/2 is disabled until the update.
Our servers are protected for now – HTTP/2 is disabled until the update.
Plesk has published a workaround for the Plesk interface. We have applied it and disabled HTTP/2 there as well. The Plesk interface is available again.
The update with the fixed nginx version 1.30.7 is still pending. As soon as it is installed, we will re-enable HTTP/2.
As no patch is currently available for the Plesk interface, we have temporarily blocked external access to it.
Plesk is preparing an update with the fixed nginx version 1.30.7. As soon as it is installed, we will restore access.
On 18 November 2026, five vulnerabilities in the nginx web server were published under the name “NGINX2Root”. nginx is one of the most widely used web servers and reverse proxies and is also part of many hosting platforms. The vendor F5 rates all five flaws 9.2 out of 10 under CVSS 4.0.
Without authentication, attackers can crash nginx processes. Security researchers have also shown that, under certain conditions, code can be executed on the server. Exploit code is publicly available, but no actual attacks have been reported so far.
nginx versions 1.9.5 to 1.31.8 are affected. The flaws are fixed in versions 1.30.7 and 1.31.9 and in the updates of the Linux distributions, some of which are still pending.
Which flaw applies depends on the configuration:
| CVE | Affected if … | Our servers |
|---|---|---|
| CVE-2026-123007 | HTTP/2 is enabled | Mitigated (HTTP/2 off) |
| CVE-2026-123633 | HTTP/2 is enabled and nginx passes requests to a backend | Mitigated (HTTP/2 off) |
| CVE-2026-123634 | the backend server name contains variables and SSI or mirror is used as well | Not relevant in the standard configuration |
| CVE-2026-121810 | HTTP/3 is enabled | Not affected (no HTTP/3) |
| CVE-2026-113425 | nginx runs as a mail proxy | Not affected (no mail proxy) |
Right after the disclosure, we disabled HTTP/2 for all websites on our web hosting servers and on our other servers running nginx. This means the two most serious flaws can no longer be exploited. We do not use HTTP/3 or the nginx mail proxy, and the proxy configuration required for CVE-2026-123634 is not part of our servers’ standard configuration. The Plesk administration interface also uses nginx; following a workaround from Plesk, we have disabled HTTP/2 there as well. Your websites remain fully available; browsers temporarily connect via HTTP/1.1 instead of HTTP/2. As soon as fixed packages are available, we will install them and re-enable HTTP/2.
For websites in our web hosting, no action is required. If you have added your own nginx directives with SSI or mirror in Plesk, please contact us.
If you run nginx yourself, for example on a virtual server, update it to a fixed version or your Linux distribution’s update and then restart nginx – a reload is not enough. If no update is available yet, temporarily disable HTTP/2 by removing http2 from the listen lines or deleting http2 on;. If software or a container ships its own nginx, the vendor’s updates apply.
This command shows whether nginx is built with HTTP/2 support:
nginx -V 2>&1 | grep -o with-http_v2_module
This command shows whether HTTP/2 is enabled in the configuration (no output means: off):
nginx -T 2>&1 | grep -nE 'listen.*http2|http2[[:space:]]+on'
Our support team will be happy to help if you have any questions.
nginx security advisories (opens in a new tab) Plesk advisory (opens in a new tab)
Whether it’s a specific question or a new project – we’re happy to help.