PHP released versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026. Together they fix 18 CVEs. Seven are rated Critical at CVSS 9.2, and The Hacker News and SecurityWeek report that the critical bugs can lead to remote code execution. The PHP security team pre-announced the release a day earlier, saying the critical issues need non-default configuration or uncommon setups.

Dave Jong, Security Research Lead at Patchstack, checked each fix against WordPress. His finding: that statement holds for most of the bugs. But two are reachable on setups that are ordinary on WordPress hosting, and a third relied on a setting that was on by default in every PHP build until this release. None of the 18 is in CISA's Known Exploited Vulnerabilities catalogue at the time of writing. The release lands four weeks after the PHP2Shell patches, which SecurityWeek says were widely exploited.

At a glance: PHP Nov 2026 release: 18 CVEs incl. CVE-2026-129496. Critical · CVSS 9.2 (7 of 18). Exploited: No known attacks; not in CISA KEV. Affected: PHP 8.2, 8.3, 8.4 and 8.5 before the new releases; PHP 8.1 and older get no fixes. What to do: Update to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36.

What is affected

These are PHP bugs, not WordPress bugs. Updating WordPress or its plugins does nothing for them. The fix is a server-level PHP update. The fixes apply to any site on these PHP versions, though Patchstack's reachability analysis covers WordPress only.

  • PHP 8.2, 8.3, 8.4 and 8.5 before the releases above. Some bugs affect only 8.5, or only 8.4 and 8.5.
  • PHP 8.1 and earlier are end of life and received no fixes. Every flaw that affects 8.2 stays open on them permanently.

What goes wrong

Two bugs stand out for WordPress sites.

  • Timezone cache use-after-free (CVE-2026-129496). When PHP writes an early startup warning to a file-based error log, it can keep a pointer to memory that has already been freed. PHP-FPM and mod_php workers inherit that stale pointer. Triggers include an invalid timezone setting or a deprecation notice, followed by a warning any visitor can cause, such as sending a very large form. Researchers crashed an FPM worker on default settings and showed code execution under both FPM and mod_php. It needs no login and nothing from your application, so no code change can block it.
  • PHP-FPM request smuggling (CVE-2026-129289). If the web server reuses its connections to PHP-FPM, leftover data from a malformed request can be treated as a new request. The advisory says this can run attacker-controlled PHP, bypass front-end routing and spoof client addresses. WordPress meets the application-side condition on every REST API request and in xmlrpc.php, so exposure comes down to one web server setting.

The session upload progress setting was on by default since PHP 5.4.0 and is now off. It lets an anonymous visitor make PHP write a session file under an ID they choose. Two session bugs (CVE-2026-126714 and CVE-2026-115560) build on this, but they also need a plugin that reads sessions back, which Patchstack calls very rare. The more practical risk is hosts where several sites share one session folder.

The rest is narrower. CVE-2026-129291 (High, 8.8) lets someone who already has code running in a PHP worker, for example through a vulnerable plugin, gain control of the FPM master process, usually root. It needs catch_workers_output, which the official PHP-FPM Docker images enable. Two HTTP stream wrapper bugs only matter if a plugin fetches remote URLs with file_get_contents() or fopen() instead of wp_remote_get(). The SOAP, PHAR, DOM and CGI fixes are not reached by WordPress core.

Why it matters

Patchstack's view is that the PHP update should not wait for your next maintenance window. A file-based error log with startup warnings is a configuration many sites drift into after a PHP version change. FastCGI connection reuse is a common performance tweak. On managed hosting, your host controls both, so you may need to ask them.

What to do now

Update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, matching your branch. If you are on 8.1 or older, plan a move to a supported branch. If you cannot update straight away, Patchstack lists these interim steps in order of value:

  • Set session.upload_progress.enabled=0 in server configuration for every pool and virtual host. Setting it in application code is too late.
  • Turn off FastCGI connection reuse: fastcgi_keep_conn off in nginx, or enablereuse=off for Apache's mod_proxy_fcgi.
  • Clear any startup warnings PHP is logging, restart the FPM master and all workers, and consider logging errors to syslog instead of a file.
  • Set catch_workers_output = no on pools that do not need it, especially in container images.
  • On PHP 8.5, confirm zend.exception_ignore_args=On is really in effect, including pool overrides and .user.ini files.
  • Give each site its own session.save_path. Separate FPM pools do not get separate session storage by default.

After patching, review your plugins for the patterns core avoids: fetching remote URLs with file_get_contents(), talking to SOAP services, or calling session_start(). That is where any remaining application-level exposure will sit.

Not sure if this affects you? Talk to us and we will check your sites and servers and plan the update with you.

Sources