Skip to content

What to ask your host about this week’s NGINX and PHP fixes

Two serious NGINX HTTP/2 flaws and PHP’s 19 November security releases are fixed by your host, not by updating WordPress. Here’s what to ask them.

5 min readSouthWest WebPress team

Two sets of server security fixes landed this week. NGINX released updates on 18 November 2026 for two serious HTTP/2 flaws, one rated critical. PHP followed today, 19 November, with releases fixing 18 vulnerabilities. Updating WordPress or your plugins won’t fix either. Both sit in the software your host runs underneath your site, so this week the job is to confirm your provider has patched.

This follows our recent posts on the Apache HTTP/2 flaw and on the earlier PHP and Brotli issues. NGINX is the other widely used web server for WordPress sites, often in place of Apache. Every WordPress site runs on PHP.

What’s been fixed in NGINX

NGINX has released version 1.31.9 (mainline, the branch with the newest features) and version 1.30.7 (stable). For both HTTP/2 flaws, any version below these is vulnerable. HTTP/2 is the newer way browsers and servers exchange web pages, and it is switched on for a large share of sites.

The security firm Xint reported five NGINX vulnerabilities under the name “nginx2root”. Two of them matter for most WordPress sites:

  • CVE-2026-123007, memory corruption in HTTP/2 flow control. NGINX rates it “major”. Rapid7 scores it 9.2 out of 10 (Critical). An attacker who isn’t logged in could use it to leak data, crash the web server, or run their own code with the permissions of the NGINX worker process. The bug has been in NGINX since version 1.9.5 in 2015, when HTTP/2 support was first added. HTTP/2 being switched on is the only condition it needs.
  • CVE-2026-123633, a “use-after-free” bug in HTTP/2, where the server reuses memory it has already released. NGINX rates it “medium”, while Xint describes it as critical. It needs HTTP/2 plus NGINX passing requests on to a backend server. Xint says that setup is common in production. It is also the usual arrangement when NGINX sits in front of PHP and WordPress.

Xint also showed that CVE-2026-123007 could be combined with a separate Linux kernel flaw to take full control of the server, and to break out of a Docker container.

How worried to be about NGINX

Rapid7 has published working proof-of-concept code, meaning attack code that shows the flaw is real. In its tests against NGINX 1.31.8 it was able to run its own code on the server. That is a good reason to patch promptly.

Rapid7 is also clear that the attack is hard to carry out in practice:

  • It needs roughly 128 GB of HTTP/2 traffic.
  • On a connection slower than about 300 Mbit/s, it can’t finish within NGINX’s default one-hour connection limit.
  • It probably won’t work if the connection passes through a proxy first.
  • Rapid7’s method depends on a specific type of processor, and no other route to running code is currently known.

Nothing we have read reports these flaws being used in real attacks. It isn’t confirmed whether a CDN (a service such as a content delivery network that sits in front of your server) fully protects you. Xint advises testing the origin server directly as well.

One more detail argues for patching rather than watching. Attacks on CVE-2026-123007 may leave little trace in NGINX’s access logs, because the traffic involved isn’t recorded as normal page requests.

What’s in the PHP releases

According to Patchstack’s analysis, PHP released versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36 today, fixing 18 vulnerabilities. Seven are rated Critical. In its advance notice, PHP said the critical issues “require either non-default configuration or uncommon setups”. We haven’t yet checked these details against php.net directly.

Patchstack picks out two bugs as the most relevant to WordPress. It rates both as “uncommon” on WordPress setups:

  • PHP-FPM request smuggling (CVE-2026-129289). PHP-FPM is the component that runs PHP behind NGINX. WordPress meets the condition for this bug on every REST API request and through xmlrpc.php. Whether a server is actually exposed depends on the web server reusing its connections to PHP. In NGINX that setting is fastcgi_keep_conn on, and in Apache it is enablereuse=on. This is where the NGINX and PHP halves of this week’s news meet.
  • Timezone cache flaw (CVE-2026-129496). This needs no login and has nothing to do with WordPress itself. It is triggered when PHP shows a diagnostic message at startup while writing its error log to a file. Patchstack says many sites drift into that setup after a PHP version change. Researchers showed it could be used to run code.

A few other fixes are worth knowing about:

  • Session upload progress. This setting was on by default in every PHP build until now, and is off from 8.4.28 onwards. It is linked to two session bugs (CVE-2026-126714 and CVE-2026-115560). Patchstack rates these “very rare” for WordPress. The real concern is shared hosting, where customers share the same session storage.
  • Privilege escalation (CVE-2026-129291). This only matters once an attacker is already in, for example through a vulnerable plugin. It could then let them gain root-level control. It depends on a setting that is on in the official PHP-FPM Docker images.
  • The remaining fixes. Patchstack says WordPress core doesn’t reach them. Any exposure would come through plugins that handle things like fetching URLs in unusual ways.

PHP 8.1 and earlier are end of life and received no fixes. Every one of these bugs that affects 8.2 affects those older versions permanently.

What you should do

If we look after your website

Server patching is part of our hosting and care work, so you don’t need to take any action. If you’d like confirmation of the NGINX and PHP versions on your server, just ask us.

If you manage hosting yourself, or use a budget host

Send your provider these questions:

  1. Do you run NGINX for my site, and is HTTP/2 enabled? If so, has it been updated to 1.31.9 or 1.30.7, or to a package that includes the fixes for CVE-2026-123007 and CVE-2026-123633?
  2. Can you check the package version, not just the NGINX version number? Linux distributions often patch without changing the number, so a fixed server can still report an old version. Ubuntu 24.04 ships 1.24.0, Ubuntu 22.04 ships 1.18.0 and Debian 12 ships 1.22.1. The reliable check is the full package version against the distribution’s security notice. We haven’t confirmed whether every distribution has published patched packages yet, so ask when the fix will be applied if it isn’t available now.
  3. Was NGINX restarted after updating? Reloading the configuration doesn’t replace the running program.
  4. If there is a CDN or proxy in front, was the origin server checked too?
  5. Which PHP version is my site on, and has it been updated? It should be on 8.5.13, 8.4.28, 8.3.37 or 8.2.36. If you are on PHP 8.1 or older, ask about a move to a supported version.
  6. Until PHP is patched, have you applied the interim steps? Patchstack suggests turning off FastCGI connection reuse and session upload progress. It also suggests clearing startup diagnostics and restarting PHP-FPM, and setting catch_workers_output = no.
  7. On shared hosting, is my session storage kept separate from other customers’?

A good host should be able to answer all of these in a single reply. If yours can’t, or the answers are vague, that tells you something about how your server is looked after. If you’d like your site on hosting where this is handled for you, our managed hosting covers server-level patching like this.

Keep reading

All posts
Security5 min read

What to ask your host about the Apache HTTP/2 flaw

A critical flaw in Apache’s HTTP/2 module sits below WordPress, so plugin updates won’t fix it. Here is how to check your server and what to ask your host.

Security5 min read

Update to WordPress 7.1.5 for 20 security fixes

WordPress 7.1.5, released 18 November 2026, fixes 20 security issues three weeks after 7.1.4. What it fixes and how to check your site has updated.

Let’s talk about your website

Book a call with our team. We will talk through your business, your goals and how your website can do more for you – then recommend a clear next step.