---
title: "The NGINX and PHP security update"
url: "https://ploi.io/news/the-nginx-and-php-security-update"
published: "2026-11-19"
last_updated: "2026-11-19"
---

# The NGINX and PHP security update

Two security releases landed this week that affect almost every Ploi server. NGINX fixed five vulnerabilities known as NGINX2Root on November 18, and PHP publishes a critical security release today, Thursday November 19. This post explains what each one means for your servers and how to install the fixes.

NGINX2Root
----------

The [NGINX2Root](https://nginx2root.com/) vulnerabilities are CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. The most serious one lets an attacker run commands on your server over HTTP/2 without logging in. The researchers also chained it with a separate Linux kernel bug to get root access. Ploi turns on HTTP/2 for every site with a certificate. The bug goes back to 2015, so assume every server runs a vulnerable version until you update it.

NGINX 1.30.7 (stable) and 1.31.9 (mainline) contain the fixes. Ploi installs the stable branch, so you need 1.30.7 or newer. Check the version on your server with:

```
nginx -v
```

Update NGINX in Ploi
--------------------

Ploi has installed NGINX from the official nginx.org repository since the summer of 2023. For those servers the update is two clicks:

- Open your server, go to **Manage**, open the **Updates** tab and click **Run updates now**. This installs every pending package update, NGINX included. Available on paid plans.
- Go back to the **General** tab and click **Restart NGINX**. A reload keeps the old program running. A restart starts the patched one.

Load balancers run NGINX too, update them the same way. Servers with automatic updates install the new version on their next run, but this one is worth doing by hand today.

On the free plan, or if you prefer SSH, [log in as root](https://ploi.io/documentation/ssh/how-do-i-login-as-root-user) and run:

```
apt-get update
apt-get install --only-upgrade -o Dpkg::Options::=--force-confold nginx
nginx -t && service nginx restart
```

Servers created before the summer of 2023
-----------------------------------------

Older servers got NGINX from Ubuntu or from the `nginx/stable` PPA. That PPA stopped publishing years ago and has no packages for Ubuntu 22.04 or newer, so running updates does not bring these servers to 1.30.7. Check which repository your server uses:

```
grep -rs "nginx.org/packages" /etc/apt/sources.list.d/
```

No output means the server does not use nginx.org yet. Switch it over as root with the same steps Ploi runs on new servers. We tested them on Ubuntu 22.04 with an NGINX install from that time:

```
rm -f /etc/apt/sources.list.d/nginx-ubuntu-stable-*.list
curl -fsSL https://nginx.org/keys/nginx_signing.key | gpg --dearmor --yes -o /usr/share/keyrings/nginx-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/nginx-archive-keyring.gpg] https://nginx.org/packages/ubuntu $(lsb_release -cs) nginx" > /etc/apt/sources.list.d/nginx.list
printf "Package: *\nPin: origin nginx.org\nPin: release o=nginx\nPin-Priority: 900\n" > /etc/apt/preferences.d/99nginx
apt-get update
apt-get install -y -o Dpkg::Options::=--force-confold nginx
rm -f /etc/nginx/conf.d/default.conf
nginx -t && service nginx restart
```

Your own NGINX configuration stays in place. The switch removes Ubuntu's module packages for image filtering, GeoIP2, XSLT, mail and stream. The nginx.org build has mail and stream built in. If one of your sites uses a directive from the other modules, `nginx -t` reports it as unknown. `nginx -t` may also warn that `listen ... http2` is deprecated. That warning is harmless.

The first command also fixes a quieter problem. A server that still lists the old PPA fails on `apt-get update`, which can stop its regular updates as well.

Ubuntu 20.04 and older
----------------------

nginx.org does not build 1.30.7 for Ubuntu 20.04. The newest version there is 1.28.0. Ubuntu 20.04 and older no longer get free security updates either, so the fix is a new server on Ubuntu 24.04 or 26.04 with your sites moved to it.

Until you have moved, removing `http2` from the `listen` lines in the NGINX configuration of each site closes the HTTP/2 vulnerabilities, the most serious one included. The others stay open.

The critical PHP security release
---------------------------------

PHP publishes security releases for all supported versions today, Thursday November 19, between 14:00 and 14:30 UTC. The PHP team [rates the most serious issues as critical](https://www.php.net/archive/2026.php#2026-11-18-1) and says they need a non-default configuration or an uncommon setup. They publish the technical details and the fixed version numbers with the release.

Ploi installs PHP from Ondřej Surý's repository, which usually has the new packages a few hours after the release. Once they are out, update in one of these ways:

- Open your server, go to **PHP** and click **Patch** next to every installed PHP version.
- Go to **Manage**, open the **Updates** tab and click **Run updates now**. This covers NGINX and PHP in one go if you wait until the PHP packages are available.

Servers with automatic updates install the new PHP versions on their next scheduled run.

The Linux kernel
----------------

NGINX2Root only reaches root with the help of a kernel bug. Ubuntu ships the kernel fix with its regular security updates once it is out. Reboot your servers after Ubuntu installs it, since only a reboot loads a new kernel.

If your setup runs into something this post does not cover, [contact our support](https://ploi.io/support) and we will help you through it.