• Mercoledì, Novembre 18, 2026

On 18 November 2026 the nginx project released security updates for five critical vulnerabilities known as nginx2root (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425, CVSS 9.2). They can allow an attacker to run code on a server without logging in. The most widespread one affects any nginx with HTTP/2 enabled, which is the usual setup for HTTPS websites.

Status at MMITech

  • Our infrastructure, including the Plesk web hosting servers and our own websites, has been updated and patched.
  • Servers of customers with a managed server contract have also been updated.
  • Web hosting and managed server customers do not need to take any action.

Unmanaged VPS and dedicated server customers

The software on these servers is maintained by you, so we cannot update it for you. If nginx runs on your server, please update it as soon as possible.

Fixed versions: nginx 1.30.7 (stable), 1.31.9 (mainline) or newer, or a distribution package that includes the fix.

Important: at the time of writing (evening of 18 November 2026), Ubuntu, Debian and Red Hat based distributions (AlmaLinux, Rocky) had not yet published fixed nginx packages. If you use the nginx package of your distribution, a normal system update does not fix this yet. Use the temporary protection below until the package is released, or switch to the official nginx.org packages.

How to update:

  • nginx.org packages (Ubuntu / Debian): sudo apt update && sudo apt install --only-upgrade nginx, then sudo systemctl restart nginx.
  • nginx.org repository after a release upgrade: if you ever upgraded Ubuntu to a new release (for example 22.04 to 24.04), check that the nginx.org repository is still enabled. Release upgrades disable it, and nginx then silently stops receiving updates.
  • Distribution packages (Ubuntu, Debian, AlmaLinux, Rocky): install the security update as soon as your distribution publishes it, then restart nginx. Until then, use the temporary protection below.
  • Plesk: Plesk ships its own nginx. Install the Plesk update as soon as it is available: Tools & Settings > Updates.
  • Docker: pull a fixed image (nginx:1.31.9 or nginx:1.30.7) and recreate the container. Restarting alone keeps the old nginx. Older tags such as nginx:1.27 will not receive a fix, so change the tag.
  • Always restart nginx after updating. A reload is not enough, because old worker processes keep running.

How to check: nginx -v shows the version. Distribution packages keep the old version number even when patched, so compare the package version with your distribution’s security notice. To see whether HTTP/2 is enabled: sudo nginx -T 2>&1 | grep -E 'listen.*http2|http2 on'

If you cannot update today: turn off HTTP/2, and HTTP/3 if you use it. On nginx 1.25.1 or newer set http2 off;. On older versions remove http2 from all listen lines. Then restart nginx. Websites keep working over HTTP/1.1. This only reduces the risk and does not cover all five vulnerabilities; updating is the only real fix.

Linux kernel: the researchers also reported a related Linux kernel flaw (SCTP) that can turn an nginx compromise into full root access. No kernel fix is available yet. If you do not use SCTP, block the module: echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf

Full advisory: nginx.org and Xint

 

If you need help, please open a support ticket.