Executive summary
On 21 October 2026, the PHP project published a security release covering two critical remote-code-execution vulnerabilities in supported PHP branches. The official advisory identifies CVE-2026-109618, an out-of-memory corruption issue, and CVE-2026-109619, a stale global state issue. Both can be reached through a web request before application code has run.
The safe action is to upgrade every web-serving PHP installation to the fixed release for its branch, restart the PHP workers, and verify that the process actually loaded the new binary. Configuration mitigations can reduce exposure while a change is being prepared, but the PHP project says there is no complete configuration-only mitigation.
What happened on 21 October 2026
The PHP security release applies to supported PHP 8.2, 8.3, 8.4 and 8.5 branches. The advisory describes the vulnerable paths as reachable by an unauthenticated HTTP request on installations that serve web traffic, including common mod_php and PHP-FPM deployments. An attacker does not need to reach a Laravel controller for the vulnerable PHP process to be involved.
The practical risk depends on how PHP is deployed, which request features are enabled, whether the service is reachable from the internet, and what operating-system permissions the PHP worker has. A private CLI-only PHP installation is a different exposure profile from a public web worker, but it should still be upgraded when the package source provides the fix.
The two critical vulnerabilities
CVE-2026-109618 — remote code execution through OOM corruption
The PHP advisory describes a memory-corruption condition related to out-of-memory handling. A carefully constructed request can cause corruption in the PHP process and may lead to remote code execution. Because the trigger is handled by the PHP runtime, the application can be affected before normal framework validation or authentication executes.
CVE-2026-109619 — remote code execution through stale global state
The second issue involves stale global state that can be influenced through a web request. The result is another path to remote code execution in affected web-serving PHP installations. The important operational detail is the same: an application-level patch cannot remove a vulnerability in the interpreter process.
Fixed PHP versions
Upgrade to the first fixed release for the branch you run. Do not choose a version only because it is the newest number in a blog post; choose a supported branch that your application and operating-system packages can run, then plan a branch upgrade separately if required.
| PHP branch | Fixed release | Security support through |
|---|---|---|
| PHP 8.5 | 8.5.12 | 31 December 2029 |
| PHP 8.4 | 8.4.27 | 31 December 2028 |
| PHP 8.3 | 8.3.36 | 31 December 2027 |
| PHP 8.2 | 8.2.35 | 31 December 2026 |
Who may be affected
- Public websites and APIs running PHP through PHP-FPM, Apache mod_php, or another web-serving SAPI.
- Laravel, Symfony, WordPress, Drupal, custom PHP, and other applications that accept requests through the affected PHP process.
- Containers and managed hosts where the application image or runtime package has not been rebuilt since the fixed release.
- Shared hosting accounts where PHP is selected in a control panel but the host has not confirmed the patched package.
A Composer lockfile does not prove that the runtime is patched. `php -v` from a deploy shell can also be misleading when the web server uses a different PHP-FPM pool or container. Check the binary and SAPI that actually serves the application.
Check the PHP version and runtime path
Start with the CLI version, then compare it with the PHP-FPM or Apache runtime used by the site. On a Laravel server, also record the PHP binary path, loaded configuration file and active service before changing anything.
php -v
php --ini
command -v php
# Debian/Ubuntu examples: inspect the service that serves web traffic
systemctl status php8.3-fpm --no-pager
php-fpm8.3 -i | grep -E 'Loaded Configuration File|PHP Version'
- Record the version shown by the application’s actual SAPI, not only your local development machine.
- Check whether the server uses a distro package, an official PHP repository, a container image, or a hosting-provider runtime.
- After patching, restart the relevant PHP-FPM, Apache, container, or worker process so old workers do not remain resident.
Assess exposure before and after patching
Review the web server access logs, PHP-FPM logs, container logs and hosting-provider security notices for unusual requests or worker crashes around the vulnerable period. The absence of a visible error does not prove that a request was harmless, so preserve logs before rotating or deleting them.
After the update, confirm the fixed version through the same request path used by the application. A health endpoint that reports only the framework version is not enough; use a controlled server-side check, a deployment record, or a runtime diagnostic that is not publicly exposed.
# Composer checks package advisories; it does not replace a PHP runtime check
composer audit
# Laravel production cache rebuild after the runtime change
php artisan optimize:clear
php artisan config:cache
php artisan route:cache
php artisan view:cache
Patch safely in production
- Identify every web-serving PHP runtime, including blue-green nodes, queue containers, cron hosts and staging environments that can reach production credentials.
- Take a tested backup of application data and configuration secrets, and confirm you can roll back the application release if a runtime change exposes an compatibility issue.
- Upgrade the PHP package or container base image to the fixed branch release supplied by your vendor.
- Run application smoke tests: login, API authentication, file uploads, queues, scheduled jobs, payments, webhooks and push-notification jobs.
- Restart PHP-FPM, Apache, container tasks and long-running workers, then verify the running version and service health.
- Record the patched version, package source, deployment time and test result so the change is auditable.
If an immediate upgrade is impossible, apply the temporary mitigations listed by the PHP advisory at the server level while the patch window is arranged. These include avoiding an unlimited memory limit, keeping post size low, disabling session upload progress where it is not required, and placing the process inside an appropriate cgroup boundary. Do not treat RLIMIT_AS or RLIMIT_DATA as a complete substitute, and do not leave a mitigation in place as the final fix.
Laravel production considerations
Laravel 13 requires PHP 8.3 or newer, so a Laravel 13 deployment should move to at least the fixed PHP 8.3.36 release or a later supported branch. Keep the web root pointed at the application’s `public` directory, keep `APP_DEBUG=false`, and rebuild Laravel’s cached configuration after the runtime is changed.
A PHP upgrade is also a good time to verify that queue workers and scheduler processes were restarted. They are long-lived processes and can continue using the previous runtime or loaded code until they are recycled.
# Example deployment checks
php artisan about
php artisan test --without-tty
php artisan queue:restart
# Confirm production debugging is disabled
grep '^APP_DEBUG=' .env
If you suspect compromise
Treat unexplained web-worker crashes, new processes, modified PHP files, unexpected admin accounts, outbound connections, or changed scheduled jobs as incident signals. Do not simply delete suspicious files and continue operating: that can destroy evidence and leave credentials exposed.
- Restrict public access or isolate the affected host while preserving a forensic copy and relevant logs.
- Rotate application, database, cloud, payment, SSH and deployment credentials from a known-clean system.
- Review recent deploys, file changes, cron entries, systemd units, user accounts, SSH keys and outbound connections.
- Rebuild the host or container from a known-good source instead of trusting a manually cleaned runtime.
- Notify affected stakeholders and document the timeline, indicators, containment actions and validation evidence.
Long-term PHP security checklist
- Subscribe to PHP, operating-system, framework and hosting-provider security advisories.
- Keep supported PHP branches in production and make the branch upgrade part of the roadmap before security support ends.
- Use immutable or repeatable builds so every server receives the same patched runtime.
- Keep web workers least-privileged and separate from deployment credentials and unrelated services.
- Centralise access logs, PHP-FPM errors, process events and deployment records with retention appropriate to the risk.
- Test backup restoration and rebuild procedures before the next emergency patch arrives.