PHP 7.0 ended on 10 January 2019 at 7.0.33. There is no upstream PHP2Shell tag and no PHP project source backport for 7.0.
Lifecycle
PHP 7.0 reached end of life on 10 January 2019. The reference point from php.net is 7.0.33. 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.0 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.0. PHP’s list of minimal source backports stops at 7.4, 8.0, and 8.1.
Vendor packages
Ubuntu 16.04 ESM lists php7.0 fixed in 7.0.33-0ubuntu0.16.04.16+esm22. That is an Ubuntu package revision on top of 7.0.33, available through Ubuntu Pro legacy coverage according to Ubuntu’s post. It does not mean every 7.0.33 binary on other distributions is fixed.
Nginx, Apache, and PHP-FPM
Nginx and Apache only route the request. On PHP 7.0, 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.0 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.0 and a newer PHP side by side is only fixed for the vhost you actually updated.
Remediation paths
On Ubuntu 16.04, compare the package with USN-8948-2 and restart Apache or PHP-FPM. On any other 7.0 host, confirm the vendor separately. If they have no errata, plan a migration.
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.0 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.0 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.0 release a PHP2Shell fix?
PHP 7.0 ended on 10 January 2019 at 7.0.33. There is no upstream PHP2Shell tag and no PHP project source backport for 7.0.
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.