Discuss a project
  1. Home
  2. Blog

Nginx and PHP vulnerabilities in November 2026: how to protect your website

NGINX2Root and critical holes in PHP: what happened on November 18–19, how to check your server and close vulnerabilities. Step-by-step instructions with commands.

Published
November 22, 2026
Nginx and PHP vulnerabilities in November 2026: how to protect your website

Nginx and PHP vulnerabilities in November 2026: what happened and how to protect your site

It’s been a tough week for everyone who has a website. On November 18, nginx developers closed a pack of critical vulnerabilities, which they called NGINX2Root. The next day, November 19, a large PHP security release was released: 18 fixes, seven of them critical.

nginx and PHP work together on a huge part of sites on the Internet, from WordPress landing pages to online stores and personal accounts. Therefore, the news concerns almost every website owner, even if he has never heard these words.

Below we will tell you what exactly broke, what we did for our clients’ sites and how to check and protect your server yourself. Instructions with commands at the end of the article.

What happened to nginx: NGINX2Root

nginx is a program on the server that accepts requests from visitors and gives them the site. It's in front of most websites, even if you don't know about it.

The NGINX2Root series includes five vulnerabilities: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425. The most dangerous of them, CVE-2026-123007, sits in HTTP/2 processing and has been in the code since 2015, that is, in all versions starting from 1.9.5. Through it, an attacker can remotely execute code on the server without any authorization if HTTP/2 is enabled on the server. And HTTP/2 is enabled almost everywhere today, because the site loads faster with it.

The remaining vulnerabilities affect HTTP/3, the domain name resolution mechanism (directive resolver) and the mail proxy. Researchers have shown that, in conjunction with a separate bug in the Linux kernel, an attacker can gain root rights, even when nginx is running inside a Docker container.

How serious is this in practice:

  • according to BI.ZONE WAF, every third nginx server in the world may be vulnerable Russia;

  • Censys counted about 8.8 million nginx servers accessible from the Internet around the world that are potentially vulnerable;

  • in the first four hours after publication BI.ZONE recorded more than 30 exploitation attempts. The attackers did not wait.

The fixes were released in versions nginx 1.30.7 (stable branch) and 1.31.9 (mainstream). Anything older needs to be updated.

What happened to PHP

PHP powers WordPress, Bitrix, OpenCart, Laravel and thousands of self-written sites. On November 19, the PHP team released fixes for all supported branches at once. The most unpleasant vulnerabilities:

  • CVE-2026-129289 - “smuggling” of requests in PHP-FPM. If the web server maintains a persistent connection with PHP-FPM (in nginx this is fastcgi_keep_conn on), and the application does not finish reading the request body, an attacker with one request can execute his PHP code on the server.

  • CVE-2026-115560 - a bug in the session mechanism and tracking file download progress, which leads to remote code execution under certain session settings.

  • CVE-2026-126714 (phpAfterShell) - corrupted session files turn into the ability to execute arbitrary code.

  • a few more use-after-frees in the PHP core, date module and FPM.

Important detail: if you updated PHP in October, this is not enough. The November fixes are only available in versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (and the new 8.6.0). For PHP 8.1 and older versions there are no fixes from the developers at all.

What we did

Some of our clients' sites live on servers that we configure and maintain ourselves. As soon as the security bulletins appeared, we got to work, without waiting for any of the clients to ask.

What we did on the servers we manage:

  1. We checked each server and found out what versions of nginx and PHP are there, whether HTTP/2 and HTTP/3 are enabled, what modules are running. Didn't rely on the version number: some Linux distributions build in patches without changing the number.

  2. Updated nginx to patched versions and rebuilt containers where nginx runs in Docker.

  3. Updated PHP and PHP-FPM to the November versions and restarted all worker processes.

  4. Checked the settings through which the attacks work: persistent connections to PHP-FPM, session processing, availability of PHP-FPM from network.

  5. Look at the logs for traces of attacks: nginx worker process crashes, strange outgoing connections, new PHP files in site folders.

  6. Made sure that the backups are fresh and from them you can recover.

We wrote to clients whose sites are on someone else’s hosting or on our own servers: we explained what happened, how this threatens their project, and helped check and update the server or suggested what to ask the hosting provider.

If we created your site, but you did not receive any messages from us, write to us, we'll check.

How to understand that your site is at risk

Your site is most likely affected if:

  • it runs on its own server or VPS (and not on a constructor like Tilda);

  • on the server there is nginx older than 1.30.7 / 1.31.9;

  • site on PHP, and the PHP version has not been updated after 19 November;

  • the server has not been served by anyone for a long time.

If the site is run by a contractor or hosting provider, write to him today. You can do this:

Good afternoon On November 18–19, fixes for critical nginx (NGINX2Root, CVE-2026-123007) and PHP (CVE-2026-129289, CVE-2026-115560) vulnerabilities were released. Tell me, are updates installed on the server of our site? If not, when are you planning to?

Be careful: in such weeks there are always scammers who write on behalf of the “hosting security service” and ask for access or payment for “emergency treatment”. A real contractor will not ask you to send a password to the messenger.

Instructions: how to protect your server from NGINX2Root and PHP vulnerabilities

The commands below are designed for Ubuntu and Debian, the most common VPS systems. They need to be executed as root or via sudo. If you are not confident in your actions on the server, it is better to entrust this to a specialist: an error in the configuration can destroy the site.

Step 1. Make a backup copy

Before updating anything, save the site files, database and configs:

bash

tar -czf /root/backup-site-$(date +%F).tar.gz /var/www /etc/nginx /etc/php
mysqldump --all-databases > /root/backup-db-$(date +%F).sql

Download copies to yourself, and don’t just leave them on the same server.

Step 2. Find out the nginx version and what’s in it enabled

bash

nginx -v
nginx -T 2>/dev/null | grep -E 'http2|http3|quic|resolver|mail'

If the version is lower than 1.30.7 (or lower than 1.31.9 for branch 1.31) and the output contains http2 , the server is vulnerable to the most dangerous bug.

The version number does not always tell the truth. Ubuntu и Debian часто переносят исправления в старую версию без смены номера. Проверьте журнал изменений пакета:

bash

apt changelog nginx 2>/dev/null | grep -m5 CVE-2026-123007

If the CVE is in the log, the fix is already installed.

Step 3. Update nginx

bash

apt update
apt install --only-upgrade nginx
nginx -t && systemctl restart nginx
nginx -v

If nginx was installed from the official repository nginx.org, the command is the same, the update will come from there. If your distribution has not yet released a fix, connect the nginx.org repository or temporarily disable HTTP/2 (step 4).

nginx in Docker. System updates do not affect nginx inside the container. You need to download a fresh image and recreate the container:

bash

docker compose pull
docker compose up -d
docker exec  nginx -v

The same applies to Nginx Proxy Manager and any images that contain nginx.

Step 4. If you can’t update nginx right now

Temporary measure: disable HTTP/2 and HTTP/3. The site will become a little slower, but the two most dangerous vulnerabilities will stop working.

In the site configs (/etc/nginx/sites-enabled/ or /etc/nginx/conf.d/) remove http2 from the line listen:

nginx

# was
listen 443 ssl http2;
# has become
listen 443 ssl;

In new versions of nginx, there may be a separate directive http2 on; instead, replace it with http2 off;. Comment out the lines with quic (HTTP/3). Then:

bash

nginx -t && systemctl reload nginx

This only protects against HTTP/2 vulnerabilities. Only an update can save you from the rest, so don’t put it off for too long.

Step 5. Find out the PHP version

bash

php -v
ls /etc/php/
systemctl list-units --type=service | grep php

One server may have several versions of PHP installed at once, check them all. Safe versions: 8.5.13, 8.4.28, 8.3.37, 8.2.36, 8.6.0 and later.

Step 6. Update PHP and restart PHP-FPM

bash

apt update
apt install --only-upgrade 'php*'
systemctl restart php8.3-fpm # substitute your version
php -v

Restart is required: while the old PHP-FPM processes are running, the vulnerable code remains in memory.

If you have PHP 8.1 or older, the update will not occur. This is a reason to move to PHP 8.3 or 8.4. Before moving, check the compatibility of the site on a test copy: old plugins and home-written code sometimes break.

Step 7. Check the settings through which the attacks work

Find persistent connections with PHP-FPM:

bash

 grep -rn 'fastcgi_keep_conn' /etc/nginx/

If there is fastcgi_keep_conn on; somewhere and you can’t update PHP yet, replace it with off or delete the line (by default the connection is closed after each request). This resolves CVE-2026-129289.

Disable loading progress tracking in sessions as a temporary protection against CVE-2026-115560. In php.ini (for example, /etc/php/8.3/fpm/php.ini):

ini

session.upload_progress.enabled = 0

Exactly in php.ini or in the FPM pool settings. Via ini_set() in code or the file .user.ini will not work: the setting must take effect before PHP starts parsing the request. After editing, restart PHP-FPM.

Make sure that PHP-FPM is not exposed to the Internet:

bash

ss -tlnp | grep php-fpm

It's good if PHP-FPM listens to a unix socket or 127.0.0.1. If you see 0.0.0.0:9000, close the port with a firewall or switch FPM to the socket.

Step 8. Check if you have already been hacked

The attacks began in the first hours, so it is not enough to update, you also need to make sure that the server is clean.

Working process crashes nginx (frequent trace of exploitation attempts):

bash

grep -E 'exited on signal (11|6)' /var/log/nginx/error.log*

New or changed PHP files over the last week, a web shell may be hidden among them:

bash

find /var/www -name '*.php' -mtime -7 -ls
grep -rlE 'eval\(base64_decode|assert\(\$_|system\(\$_' /var/www --include='*.php'

Suspicious processes and outgoing connections from the web server:

bash

ps -u www-data -f
ss -tpn | grep -E 'nginx|php-fpm'

Processes like sh, bash, curl, wget or unfamiliar binaries on behalf of www-data and Outgoing connections to unknown addresses are a reason to sound the alarm. In this case, do not try to “clean” the server manually: restore the site from a backup copy on a clean server, change all passwords and keys (database, SSH, admin, API).

Step 9. Set up protection for the future

These vulnerabilities are closed, but new ones will be found in a month. Worth doing once:

  • Automatic security updates. On Ubuntu and Debian this package unattended-upgrades:

bash

apt install unattended-upgrades
dpkg-reconfigure -plow unattended-upgrades
  • Regular backups to another server and at least once a quarter a trial recovery from them.

  • Minimum open out. Only 80 and 443 look outside, SSH - by key, not by password; databases and PHP-FPM are not exposed to the Internet.

  • Supported software versions. PHP 8.2 will stop receiving fixes on December 31, 2026, it’s worth planning the transition now.

  • WAF and monitoring. A firewall for web applications cuts off some attacks even before the server, and monitoring will report crashes and strange activity before clients do.

  • Subscribe to security bulletins nginx, PHP and your CMS to learn about problems on the day of publication, and not from the news hacks.

Frequently asked questions

My site is on Tilda / designer. Should I do something? No. The platform itself manages the designer servers.

Site on WordPress. Is it enough to update WordPress? No. WordPress is an application, and the vulnerabilities are in nginx and PHP that it runs on. The server needs to be updated. It's also worth updating WordPress and plugins, but that's a different story.

I'm on regular shared hosting. Who updates? Hosting provider. But check with support to see if nginx and PHP are updated, and switch the site in the panel to a supported version of PHP if it is the old one.

Can I just disable HTTP/2 and not update?Only for a day or two. Disabling it closes two of the five vulnerabilities in nginx and does not help with PHP problems at all.

How can I tell if the update was successful? nginx -v and php -v show the corrected versions (or the package changelog mentions the necessary CVEs), the site opens, and there are no new errors in /var/log/nginx/error.log.

Need help with server?

We at vasilyev.design make turnkey websites and take them on for maintenance: setting up a server, monitoring updates, making backups and responding to stories like NGINX2Root on the same day. The site owner does not need to understand nginx and PHP - we are responsible for this.

If your site is not being served or you are not sure that the server is up to date, write to us. We'll check the server, close the vulnerabilities and tell you what else needs to be fixed.

Ilya Vasilyev
Ilya Vasilyev

Founder, vasilyev.design

Tell me about your project — I reply within an hour

I'll ask a couple of questions and estimate timeline and cost. I lead the project myself, no managers in between.

Ilya Vasilyev

Ilya Vasilyev

Studio founder, designer and developer

About the studio