Skip to content

PHP: October 2026 security fixes

Checked on October 23, 2026. This guide covers CVE-2026-109618 and CVE-2026-109619, which can allow unauthenticated remote code execution. PHP released fixes on October 21, 2026. See the PHP security announcement.

Fixed versions

PHP branch Minimum fixed release
8.2 8.2.35
8.3 8.3.36
8.4 8.4.27
8.5 8.5.12

Use this release or a later release in the same branch. PHP 8.1 and earlier no longer receive regular PHP project support; move to a supported branch unless your vendor confirms a fix. Distribution packages may contain backported fixes, so check the vendor's advisory as well.

Update in the cloud

For managed PHP, open the security update in the server's services and follow security updates. The cloud checks package availability and restarts PHP-FPM. After completion, continue with the long-running process restarts below.

A new PHP release or an update to the cloud does not confirm that your server has been patched. Check every installed branch, including those no project currently uses.

Manually via SSH

Connect using SSH or the terminal with a user allowed to run sudo. These examples use PHP 8.4 on Ubuntu with APT packages; replace the branch number for your server. Updating and restarting FPM may briefly interrupt websites.

1. Check the version and package source

ls /etc/php
php8.4 -v
sudo apt-get update
apt-cache policy php8.4-fpm php8.4-cli

Check Installed, Candidate and the package origin. The candidate must contain the fix for that branch. If it is missing or still vulnerable, stop and check the PHP package source or contact support. Repository filenames can differ between servers.

2. Upgrade installed packages in the branch

dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package}\n' 'php8.4*' \
  | awk '$1 == "ii" {print $2}' \
  | xargs -r sudo apt-get install --only-upgrade \
      -o Dpkg::Options::="--force-confold"
sudo php-fpm8.4 -t
sudo systemctl restart php8.4-fpm
sudo systemctl is-active php8.4-fpm

Review the changes before confirming APT. --only-upgrade limits the selection to installed packages; --force-confold preserves locally modified configuration files managed by dpkg. If installation or configuration validation fails, resolve the error before running further commands. FPM steps apply only to a branch with PHP-FPM installed; for another PHP handler, restart its service instead.

Restart long-running processes

Restarting FPM does not refresh running CLI processes. Restart affected project processes, including queue workers, Horizon, Octane or Reverb. For Laravel, run the applicable command in each application's directory as its Linux user:

php8.4 artisan queue:restart
php8.4 artisan horizon:terminate
php8.4 artisan octane:reload

Run only commands for services the application uses. For workers and Horizon, verify that the process manager starts them again. Restart Reverb and other persistent processes through their process manager.

Verify the result

php8.4 -v
php-fpm8.4 -v
sudo systemctl status php8.4-fpm --no-pager

The -v output checks the binary on disk; running processes also need a successful restart. Check the website, logs and queue processing. Repeat for other PHP branches.

October 23, 2026 update

PHP recommends setting session.upload_progress.enabled=0 until the next bugfix release due to another issue involving unusual session serialization changes. Set it in the relevant web php.ini before request processing and restart PHP workers; application-level ini_set() is insufficient. See the latest PHP announcement for conditions and details. This measure does not replace the update above.