PHP 7.2 ended on 30 November 2020 at 7.2.34. There is no upstream PHP2Shell release for this branch.
Lifecycle
PHP 7.2 reached end of life on 30 November 2020. The reference point from php.net is 7.2.34. 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 7.2 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
There is no tagged upstream release that fixes PHP2Shell on PHP 7.2. PHP’s list of minimal source backports stops at 7.4, 8.0, and 8.1.
Vendor packages
Ubuntu 18.04 ESM lists php7.2 fixed in 7.2.24-0ubuntu0.18.04.17+esm14. AlmaLinux 8 lists a php:7.2 stream package, php-7.2.24-1.module_el8.10.0+4315+7b734bf3.alma.1, and notes that 7.2 is still the default module on AlmaLinux 8 and is a retired stream they chose to patch. AlmaLinux says future fixes for retired streams are not guaranteed.
Nginx, Apache, and PHP-FPM
Nginx and Apache only route the request. On PHP 7.2, 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 7.2 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 7.2 and a newer PHP side by side is only fixed for the vhost you actually updated.
Remediation paths
On those two platforms, match the package version and restart the SAPI. php -v remaining at 7.2.24 is expected for both backports. Elsewhere, verify your own vendor. Prefer a move to a supported stream after you test the application, which is what AlmaLinux illustrates with a module switch to php:8.2.
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 7.2 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 7.2 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 7.2 release a PHP2Shell fix?
PHP 7.2 ended on 30 November 2020 at 7.2.34. There is no upstream PHP2Shell release for this branch.
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.