Technician checks server equipment during the PHP November 2026 security release update Technician checks server equipment during the PHP November 2026 security release update

PHP November 2026 Security Release: What WordPress Hosts Need

PHP released fixes for 18 CVEs on November 19, including issues that can reach WordPress through common hosting configurations. Here are the two PHP flaws Patchstack says deserve attention this week, plus the server settings operators should check.

PHP released security updates for four supported branches on November 19, fixing 18 CVEs. The PHP November 2026 security release matters to WordPress operators because two issues can be reachable on hosting setups the WordPress application commonly encounters, according to Patchstack’s analysis of the release.

The fixes are in PHP, not WordPress core, so updating WordPress alone will not address them. This report explains which server-side conditions Patchstack identified, what to ask a hosting provider, and which PHP versions contain the fixes.

Short answer: Update to PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36, matching the branch your site uses. Patchstack singles out a timezone-cache use-after-free and PHP-FPM request smuggling for attention. The first depends on startup diagnostics and file-based error logging; the second depends on FastCGI connection reuse at the server front end.

What the PHP November 2026 security release means for WordPress

The release fixes 18 CVEs across PHP 8.2, 8.3, 8.4, and 8.5. Seven are rated Critical at CVSS 9.2, but severity alone does not show whether a particular WordPress server can reach a flaw. Patchstack says the release’s two most relevant concerns have conditions tied to server configuration and how PHP handles requests.

That distinction matters. These are not WordPress plugin or core vulnerabilities, and a plugin update cannot fix PHP itself. The server environment needs the PHP update, while the application and hosting configuration determine whether some specific flaws can be reached.

The two PHP issues Patchstack says deserve attention

Timezone-cache use-after-free

CVE-2026-129496 affects PHP 8.2 through 8.5 and is rated Critical. Patchstack says it can arise when a startup diagnostic is written to a file-based error log. The article describes a trigger involving a diagnostic during worker startup, such as a warning caused by a large form request, and says the issue does not depend on WordPress code.

That makes this a hosting-level concern: the relevant conditions are in PHP’s startup and logging configuration. Patchstack reports that researchers crashed an FPM worker on default settings and demonstrated code execution under FPM and mod_php with ASLR enabled. Its recommended response is to install the fixed PHP release rather than rely on an application-side workaround.

PHP-FPM request smuggling

CVE-2026-129289 is also rated Critical and affects PHP 8.2 through 8.5. It requires the front end to reuse FastCGI connections and the application to read php://input without draining the request body. Patchstack says WordPress meets the application-side condition for REST requests, so reachability depends on whether the server’s front end uses connection reuse.

Patchstack describes the risk as malformed multipart data being interpreted as another FastCGI request on a reused connection. It says the affected request could run attacker-controlled PHP as the worker user. The article’s temporary measure, if an operator cannot patch immediately, is to turn off FastCGI connection reuse. The exact setting depends on the server: Patchstack names fastcgi_keep_conn off for nginx and enablereuse=off for mod_proxy_fcgi.

Other CVEs have narrower conditions

Several of the other fixes need unusual configurations, particular PHP extensions, or plugin behavior that Patchstack says WordPress core does not use. That does not make every site automatically safe; it means the relevant question is whether the site or a plugin meets the conditions in the advisory.

IssueWhat Patchstack says is required
HTTP stream wrapper bugsA plugin must fetch a remote URL through PHP’s stream wrapper. Patchstack says core uses other HTTP paths.
Session deserializationSession data must be written under the stated conditions and then read back by code using the relevant serializer. Patchstack notes that plugins calling session_start() are uncommon.
PHP-FPM epoll use-after-freeCode execution must already have occurred inside a worker, with the specified output setting enabled.
SOAP, PHAR, DOM, and CGI issuesExposure depends on use of the affected components or configurations; Patchstack says the listed behavior is not reached by WordPress core.

The table is a guide to the conditions Patchstack describes, not a substitute for checking a server’s actual PHP configuration and installed plugins. One notable exception in the analysis is the PHP-FPM request-smuggling condition: WordPress meets the application-side requirement, leaving front-end connection reuse as the configuration to verify.

Which PHP versions contain the fixes?

The fixed releases are PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36. Operators should select the matching update for their current PHP branch. Patchstack says PHP 8.1 and earlier are end of life and did not receive these fixes.

If a site is managed by a hosting company, ask which PHP branch it runs and when the provider will apply the corresponding security release. For self-managed servers, check the PHP version used by the web server and its FPM pools, rather than assuming the command-line version is the one serving the site. Patchstack’s analysis also recommends checking for startup diagnostics, reviewing file-based error logging, and disabling FastCGI connection reuse temporarily if the update cannot happen at once.

Do not treat plugin updates as a replacement for the PHP update. Patchstack identifies these as vulnerabilities below WordPress, so fixing WordPress core or a plugin does not patch the affected PHP runtime.

FAQ

Is this a WordPress core vulnerability?

No. The CVEs are in PHP, the runtime used by WordPress. Updating WordPress core does not install the PHP fixes.

Which PHP versions should WordPress sites use after this release?

Use PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36, depending on the branch the server runs. Patchstack says PHP 8.1 and earlier are end of life and did not receive these updates.

What should I check if I cannot update PHP today?

Ask your host to confirm whether FastCGI connection reuse is enabled, and review PHP startup diagnostics and file-based error logging. Patchstack recommends turning off FastCGI connection reuse as a temporary measure for the request-smuggling issue until PHP is patched.

Next step: Check the PHP version serving your WordPress site and ask your host to apply the matching November 19 security release.

Leave a Reply

Your email address will not be published. Required fields are marked *