PHP 8.4 is fixed upstream in 8.4.27. The branch is in active support until 31 December 2026 and security support until 31 December 2028. Upstream builds before 8.4.27 are below the fix.
Lifecycle
PHP 8.4 has active support until 31 December 2026. The reference point from php.net is 8.4.27 is the fix. End-of-life status and a vendor backport are different facts. A branch can be unsupported by the PHP project and still have a distribution build that includes these two fixes.
What is confirmed about exposure
The defects are in the PHP runtime, so a PHP 8.4 process that serves HTTP is in the population PHP told users to update. mod_php is the highest-risk integration. PHP-FPM is not excluded. An application update does not change this runtime.
Upstream options
Install the fixed upstream release named above, from php.net or the Windows builds linked from the release announcement.
Vendor packages
Debian 13 trixie lists php8.4 fixed in 8.4.27-1~deb13u1. Debian sid lists 8.4.27-1 as fixed, and the tracker still showed forky’s 8.4.26-1 as vulnerable on 22 October 2026. AlmaLinux 10’s php8.4 packages are listed as php8.4-8.4.24-1.el10_2.alma.1, a backport that does not move the version to 8.4.27. AlmaLinux says to query php8.4-common.
Nginx, Apache, and PHP-FPM
Nginx and Apache only route the request. On PHP 8.4, identify whether the vhost uses PHP-FPM, mod_php, or CGI. mod_php remains the highest-risk SAPI in PHP’s advisory regardless of how old the branch is. PHP-FPM on 8.4 is still in scope for CVE-2026-109619’s session path. Restart the daemon that loaded this branch after any package change. A host with PHP 8.4 and a newer PHP side by side is only fixed for the vhost you actually updated.
Remediation paths
Install 8.4.27 for upstream builds, the trixie security package on Debian 13, or the AlmaLinux php8.4 build if that is your repository. Restart the workers that are loaded from those packages. A second PHP 8.3 pool on the same host is a separate update.
Temporary settings from the PHP advisory remain available and remain incomplete. See the mitigations page.
Production precautions
Snapshot or otherwise preserve the current packages before you change a production PHP 8.4 host. Expect a restart of php-fpm or Apache to drop active requests. If an extension fails to load, roll back and treat that as a compatibility problem, not as a reason to skip the CVE.
Validation
Query the binary the vhost uses after the restart. On backport-style packages, compare the package version rather than waiting for php -v to print a new upstream number. Check one authenticated and one anonymous application route you already know how to judge.
When to involve a specialist
Involve a specialist when PHP 8.4 is tied to a custom extension, a control-panel build, or a release process that cannot take the upstream tag directly. That is the normal case for this branch, not an edge case.
Questions
Is the last upstream PHP 8.4 release a PHP2Shell fix?
PHP 8.4 is fixed upstream in 8.4.27. The branch is in active support until 31 December 2026 and security support until 31 December 2028. Upstream builds before 8.4.27 are below the fix.
Can you help if we cannot upgrade this week?
Yes. The engagement can cover a vendor package check, exposure reduction, or a migration plan. It will not pretend a missing patch exists.