PHP releases November security fixes for app servers
PHP’s 19 November security releases are now available. The project lists 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security updates and encourages users of each branch to upgrade. For developers operating…
PHP’s 19 November security releases are now available. The project lists 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security updates and encourages users of each branch to upgrade. For developers operating a PHP or Laravel commerce app, the immediate job is to check the runtime serving production requests and deploy the appropriate patched release.
The official release announcements follow a warning issued on 18 November: the highest severity in this release round is critical, with those critical issues requiring non-default configurations or uncommon setups. That qualification matters when assessing exposure; it does not remove the need to review the update.
A new release round, including the session fix
The PHP changelog records a fix for a session serializer mismatch that can lead to remote code execution, identified as CVE-2026-115560. It also lists other security corrections, including memory-safety issues. Treat this as a release-wide patch review rather than checking a single CVE and assuming the rest are irrelevant.
The session issue had already been described in PHP’s 23 October notice. Its unusual setup combines an initial php_binary or php_serialize serializer, a runtime switch to php before starting a session, and enabled session upload progress. Today’s news is the availability of the new security releases, not a newly discovered October flaw.
Check the deployed runtime
Our recommended rollout is to inventory the PHP branch used by each application, test the matching security update, rebuild containers where applicable, and restart or redeploy the services that run it. Check the web-serving runtime as well as the command-line version: an updated build machine is not evidence that production workers have changed.
PHP 8.6.0 also launched today as a feature release. Teams do not need to combine an emergency patch rollout with a move to a new feature branch; use the relevant security release for the branch you operate and assess a broader migration separately.
Laravel’s announcement says it prepared a response for its products. Follow the current instructions for the hosting product you actually use, then verify the resulting runtime. This is guidance for app infrastructure that your team operates, not a claim that merchants must patch Shopify’s hosted platform.
20 November update: session and PHP-FPM fixes, hosting status
The 19 November changelog also identifies CVE-2026-126714, involving partially overwritten session files, and CVE-2026-129289, a PHP-FPM request-smuggling issue involving an unread request body. Review the relevant advisories for your deployment rather than treating the serializer issue as the only reason to update.
Laravel confirmed on 19 November that Cloud runs the patched 8.5.13, 8.4.28, 8.3.37 and 8.2.36 releases without customer action. Its Vapor announcement lists patched 8.5.13, 8.4.28 and 8.3.37 runtimes: native-runtime users should redeploy, while Docker users should rebuild and deploy.
In its 17:43 UTC Forge update, Laravel said Ubuntu 26.04 servers could install the patches through Runtimes → PHP → Update. Ubuntu 24.04 and 22.04 were still awaiting upstream packages at that timestamp; this is not confirmation that they remain unavailable now. Check the current provider advisory before deployment. Laravel described 20.04 and older as end of life and outside that patch rollout.
20 November, 08:00 Athens check: Forge packages by architecture
The current Forge advisory now lists patched x86 packages for Ubuntu 22.04, 24.04 and 26.04. ARM availability still differs: Ubuntu 22.04 is marked patched, while 24.04 is awaiting PHP 8.3, 8.4 and 8.5 packages, and 26.04 is awaiting PHP 8.3 and 8.5. These are the provider’s status labels at our morning check, not a guarantee that a particular server has installed them.
Forge explicitly says its automatic security updates do not patch PHP from its dedicated repository. Update each installed PHP version, verify the actual CLI and PHP-FPM versions, and restart long-running workers after deployment. For older PHP branches with backported fixes, check the installed package revision: the PHP version string alone can remain unchanged.
An update command can finish without installing a fix when the required ARM package is unavailable. Check the advisory’s current table and the package candidate before treating the server as patched. Ubuntu 20.04 and earlier remain outside the listed patch rollout.
20 November, 11:00 Athens check: remaining ARM packages available
The Forge advisory now marks Ubuntu 22.04, 24.04 and 26.04 as patched on both x86 and ARM. This supersedes the package-availability gaps recorded in our 08:00 check above. Ubuntu 20.04 and earlier remain outside this rollout.
Availability still requires action on each server: update every installed PHP version, verify the running CLI and PHP-FPM packages and restart long-running workers. Forge’s automatic security updates do not install PHP updates from its dedicated repository. A supported operating-system version alone is not evidence that an application has received the fix.
Check the timezone fix as well as the session fix
The November releases also address CVE-2026-129496, a critical timezone-cache issue affecting non-thread-safe PHP deployments. If an app runs on PHP-FPM, check the version serving web traffic after rolling out the patch. A patched command-line binary alone cannot confirm which version a running worker uses. Include container images and long-running workers in the rollout.
More from News
See all →