Two security releases landed in two days this week, and both sit below WordPress: one in nginx, the web server in front of your site, and one in PHP, the language WordPress runs on. Neither can be fixed from the WordPress dashboard. No plugin update covers them. They are fixed on the server, by you or by your host.

We spent Thursday patching our own servers, so this is a practical summary: what the two bugs are, who is really affected, how to check a server in a minute, and what to do if the fixed package has not reached you yet.

The short version

  • nginx: a memory corruption bug in HTTP/2 handling (CVE-2026-123007) affects every nginx release from 1.9.5 to 1.31.8. It needs no login. Fixed in nginx 1.30.7 and 1.31.9, released on November 18. Ubuntu shipped patched packages on November 19.
  • PHP: security releases for all supported branches came out on November 19: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Each one fixes between 12 and 17 security bugs, among them three in PHP-FPM and several that can lead to remote code execution. They also close the session upload progress bug (CVE-2026-115560) that had been public without a patch since October.
  • If you run your own server: update both packages, then restart nginx and PHP-FPM.
  • If you are on shared or managed hosting: you cannot patch this yourself. Ask your host whether both updates are installed.
  • If you cannot update nginx yet: turn HTTP/2 off until you can. Sites keep working over HTTP/1.1.

nginx: memory corruption in HTTP/2

The nginx team published ten security fixes at once on November 18. The full list is on the nginx security advisories page. For a typical WordPress server, two of them matter, and both are in the HTTP/2 code:

  • CVE-2026-123007: an overflow in the HTTP/2 flow control window that corrupts memory in the worker process. It is present in every version since HTTP/2 support was added in 1.9.5, back in 2015.
  • CVE-2026-123633: a use-after-free in HTTP/2 that can be triggered when the server runs out of worker connections. It affects 1.19.7 and later.

An attacker does not need an account or a valid session, only the ability to open an HTTP/2 connection to your server. nginx itself words the impact carefully: a crashed worker process, “or potential other impact”. The researchers who reported it go further. Xint, who named the set of bugs nginx2root, and Wiz both say they achieved remote code execution against official nginx builds, and both are keeping their exploits private. One proof of concept is public, from Rapid7, and by its own description it only works against a fresh test container. As of November 19, nobody has reported attacks on real sites.

That is a comfortable position to patch from, and it will not last. The fix is public, so anyone can compare the old and the new code.

Are you affected?

Only if HTTP/2 is switched on in nginx. It is not on in a stock nginx configuration, but most setup guides, hosting panels and SSL tutorials enable it, because it makes sites faster. This command shows every place it is enabled:

nginx -T 2>/dev/null | grep -n http2

Lines like http2 on; or listen 443 ssl http2; mean yes. No output means the two HTTP/2 bugs cannot reach you, although updating is still the right move: the same release also fixes bugs in the resolver, HTTP/3, the mail proxy and TLS request handling.

Fixed versions

Where your nginx comes fromFixed version
nginx.org packages, stable1.30.7
nginx.org packages, mainline1.31.9
Ubuntu 26.101.30.4-7ubuntu1.2
Ubuntu 26.04 LTS1.28.3-2ubuntu1.13
Ubuntu 24.04 LTS1.24.0-2ubuntu7.20
Ubuntu 22.04 LTS1.18.0-6ubuntu14.23
Ubuntu 20.04 and 18.04Ubuntu Pro (ESM) only
Debian stableNot fixed yet on November 19

The Ubuntu versions are from USN-9159-1. Notice that they do not say 1.30.7. Distributions add the fix to the version they already ship, so after a correct update nginx -v still prints 1.28.3 or 1.24.0. Do not judge by that number. Check the package changelog instead:

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

If that prints a line, the fix is installed. One thing cost us time: Ubuntu’s own archive had the new packages on Thursday morning, while the mirror our hosting provider runs was still serving the old ones, so a plain apt upgrade reported nothing to do. If you see the same, run it again a few hours later, or compare the version you get with the table above.

If you cannot update yet

Some servers will wait longer: Debian stable had no fixed package on Thursday, and control panels that ship their own nginx build follow their own schedule. One of our servers runs such a panel, and its repository had no patched nginx yet. There we turned HTTP/2 off, which closes both HTTP/2 bugs:

  • On nginx 1.25.1 and later, set http2 off;.
  • On older versions, remove the word http2 from the listen lines.
  • On a panel, use the panel’s own HTTP/2 switch, otherwise it rewrites your change.

Then restart nginx. A reload keeps old worker processes alive until their connections close. Visitors will not notice much: browsers fall back to HTTP/1.1, and pages load slightly slower on sites with many small files. Turn it back on once the patched package is installed.

Turning HTTP/2 off does nothing for the other fixes in the release, so it is a stopgap and not a replacement for the update.

What about the “root” in nginx2root?

The nginx bugs give an attacker the rights of the nginx worker, usually the www-data user, not root. The name comes from a sixth bug that Xint chained after them: a flaw in the Linux kernel’s SCTP networking code that, according to their write-up, lifts that access to root. It had no CVE and no patch when they published. Very few web servers use SCTP, so if yours does not, you can stop the module from loading by adding install sctp /bin/false to a file in /etc/modprobe.d/. Then watch for the next kernel update.

PHP: the November 19 security releases

The PHP team announced a day in advance that security releases were coming for every supported branch, with the highest severity rated critical, and they shipped on Thursday afternoon. You can read the release notes in the PHP news archive. The fixed versions are:

  • PHP 8.5.13
  • PHP 8.4.28
  • PHP 8.3.37
  • PHP 8.2.36

These releases are bigger than most. The changelog lists 12 security fixes for PHP 8.2, 13 for 8.3, 14 for 8.4 and 17 for 8.5. The ones that matter most on a WordPress server:

  • PHP-FPM: three fixes, including request smuggling through an unread HTTP request body (CVE-2026-129289) and a use-after-free that can lead to local privilege escalation (CVE-2026-129291). PHP-FPM is how almost every nginx site runs PHP.
  • Sessions: two bugs that can lead to remote code execution, one through partially overwritten session files (CVE-2026-126714) and one through a session serializer mismatch (CVE-2026-115560).
  • Date handling: a use-after-free in the timezone cache that can lead to remote code execution (CVE-2026-129496).
  • PHP-CGI: an out-of-bounds read and write during PATH_INFO correction (CVE-2026-129538), for servers that run PHP as a CGI binary.

The remaining fixes are in SOAP, PHAR, DOM and the HTTP and FTP stream handling.

PHP 8.1 and older are end of life and get no fix from the PHP project. Some distributions still patch them (Ubuntu does for its own PHP 8.1 and, with Ubuntu Pro, for 7.4), so on those systems the distribution’s package is what counts.

The session upload progress bug

One fix in the list had been awaited for weeks. CVE-2026-115560 was disclosed in October without a patch, and it lets an attacker inject data into a PHP session through the upload progress feature, which can end in code execution. PHP itself called it an unlikely route, because three things have to be true at once:

  1. The server configuration sets session.serialize_handler to php_binary or php_serialize.
  2. The application switches it to php at runtime, before it calls session_start().
  3. session.upload_progress.enabled is on, which is the default.

For WordPress sites that is good news. WordPress core does not use PHP sessions at all. Some plugins do start a session, but switching the serializer at runtime is rare. If you want to be sure, search your plugins and themes for it:

grep -rl "serialize_handler" wp-content/

No result means this one bug has no way in on your site. Update PHP anyway. The other fixes in the release do not depend on that configuration, and a server that skipped October’s releases (8.2.35, 8.3.36, 8.4.27, 8.5.12) is still open to the two bugs fixed then, which are being used in real attacks.

If you cannot update PHP yet

For the session upload progress bug, the official workaround is one setting:

session.upload_progress.enabled = 0

Put it in php.ini or in the PHP-FPM pool configuration and restart PHP-FPM. Setting it with ini_set() or in a .user.ini file is too late, because the upload is parsed before your code runs. WordPress does not use this feature, so nothing on a normal site depends on it. We have had it switched off on all our servers since October and have not seen a single side effect.

That setting covers one bug out of the list. For the PHP-FPM, timezone and session file fixes there is no switch to flip, so treat it as a way to buy a few hours, not as a replacement for the update.

How to check your own site

On shared or managed hosting

You have no access to nginx or to the PHP packages, so the job is to confirm that your host did it. In WordPress, Tools › Site Health › Info › Server shows your PHP version and the web server. Compare the PHP version with the list above. For nginx the version number tells you little, for the reason explained earlier, so ask support one direct question: are the nginx fixes for CVE-2026-123007 and the November 19 PHP releases installed on my server? A good host answers that in one line.

On your own server

  1. Update the packages (apt update && apt upgrade on Ubuntu and Debian).
  2. Confirm the nginx fix with the changelog command above, and the PHP version with php -v.
  3. Restart both services, for example systemctl restart nginx php8.5-fpm. A package that is installed but not loaded into the running process protects nothing.
  4. Open the site and check that it responds as before.

What a WordPress plugin can and cannot do here

We sell a security plugin, so we should be clear about this: no WordPress plugin, ours included, can patch nginx or PHP, and none of them sees an HTTP/2 frame. These bugs are handled before WordPress starts. What a plugin can cover is the step that usually follows a successful attack, when the intruder tries to stay: a new PHP file in the uploads folder, a modified plugin file, a new administrator. Must-Have Security blocks PHP file writes that nobody approved and scans for changed files, which helps with that second step. It does not replace the two updates above.

Frequently asked questions

My site is behind Cloudflare. Am I safe?

Mostly, for the nginx HTTP/2 bugs. Cloudflare ends the visitor’s HTTP/2 connection at its own edge, so the malformed frames never reach your server, as long as the server accepts traffic only through Cloudflare. If its IP address is known and answers directly, an attacker can skip Cloudflare entirely. Cloudflare’s own advice is to update anyway. For the PHP bugs, a CDN makes no difference.

I updated, but nginx -v shows the same version as before

That is expected on Ubuntu and Debian. The fix is backported into the existing version, and only the package revision at the end changes, for example from 1.28.3-2ubuntu1.12 to 1.28.3-2ubuntu1.13. Use the changelog command to confirm.

Does WordPress itself need an update for this?

No. Neither bug is in WordPress, in a theme or in a plugin, and there is nothing to change in the dashboard. Keeping WordPress up to date is still worth doing, it is just a different job from this one.

I use Apache, LiteSpeed or Caddy, not nginx

Then the nginx part does not apply to you. The PHP part does, whatever web server sits in front of it.

The takeaway

Both fixes are available, neither bug is being used against real sites yet, and for most servers the whole job is one package update and two restarts. Do it this week. If someone else runs your server, send them the question from this article and keep the answer.