What Happened
Google Cloud published bulletin GCP-2026-090 on 2026-11-20. It describes a PHP session upload progress vulnerability in PHP's default file-based session handler, tracked as phpAfterShell, CVE-2026-126714. The bulletin rates the issue critical.
For MSPs, the response is the part that matters. Google says disabling Session Upload Progress mitigates the primary attack path for the flaw in particular, and that self-managed containers can move to patched upstream PHP now instead of waiting for managed runtime rollouts.
The affected surface crosses four Google Cloud services, so a client with PHP running in more than one place may need more than one fix. The sections below separate what happened from what to do about it.
Timeline
- 2026-11-20: Google Cloud published bulletin GCP-2026-090, describing the vulnerability in PHP's default file-based session handler.
Who Is Affected
The bulletin names four Google Cloud services: App Engine Standard (second-generation PHP 7.2 to 8.5 runtimes), App Engine Flexible, Cloud Run and Cloud Run functions. The mitigation notes add Cloud Run jobs and worker pools, and Cloud Functions (1st gen), as deployments that need to rebuild and redeploy.
End-of-life versions are the hard edge of this. PHP 8.1 and PHP 7.2 are listed as end of life with no fix available, so clients on those versions cannot patch their way out. They need to move to a supported PHP runtime.
In practice, in scope means any MSP whose clients run PHP on these services, whether the code sits in a self-managed container or a managed runtime. The management model changes the fix, not the exposure.
Technical Details
The identifier is CVE-2026-126714, tracked as phpAfterShell. The affected product is PHP, specifically its default file-based session handler.
Affected versions as stated in the bulletin: PHP 8.5 (8.5.13), PHP 8.4 (8.4.28), PHP 8.3 (8.3.37), PHP 8.2 (8.2.36). PHP 8.1 and PHP 7.2 are end of life with no fix available.
On the attack vector, the bulletin states that disabling Session Upload Progress, session.upload_progress.enabled = 0, mitigates the primary attack path for phpAfterShell in particular.
Why the PHP Session Upload Progress Vulnerability Matters to MSPs
PHP is one of the most common runtimes in web estates, and it is often the piece nobody owns. In general, a runtime that arrives with a cloud service feels managed even when the client is still responsible for the application code and its configuration.
Patch lag is a standing problem in this class of work. End-of-life components get left in place because they still run, and they stay in place until an audit or an incident forces the issue. As a standing practice, MSPs should keep an inventory of every runtime version in client environments and know which ones are past support.
The cost lands on the MSP. A client whose PHP workload is compromised or taken offline calls the MSP first, and the hours go into containment, rebuilds and reassurance. Preventing that starts with knowing what is running and having a recovery path that works.
What MSPs Should Do
Work the list in order. Google's guidance splits by how the PHP runtime is managed, so classify each client deployment before you touch anything.
- Inventory every client PHP deployment on Google Cloud and record how the runtime is managed: self-managed container, managed runtime with automatic base image updates, or pinned to a specific patch string.
- If the application does not require tracking upload progress, disable Session Upload Progress in php.ini by setting session.upload_progress.enabled = 0.
- Where feasible, switch PHP session storage away from local filesystem handlers (session.save_handler = files) to an external store such as Redis, Memcache or a database.
- For self-managed containers, upgrade to upstream PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13, then rebuild and redeploy. Cloud Run containers and App Engine flexible custom runtimes can do this without waiting on Google-managed runtime rollouts.
- For App Engine standard (second-generation PHP 8.2 to 8.5) and Cloud Run services or Cloud Run functions with automatic base image updates enabled, apply the Session Upload Progress mitigation. Google says these receive patched PHP runtimes automatically once published.
- For App Engine flexible (managed PHP runtime), Cloud Run jobs and worker pools, Cloud Functions (1st gen) and deployments pinned to a specific patch string, apply the mitigation and plan to rebuild and redeploy once Google publishes the updated runtime images.
- For clients on end-of-life PHP 7.2 to 8.1, upgrade to a supported PHP runtime. No upstream patches will be released for PHP 8.1 or earlier.
How EnterProtect Helps
EnterProtect covers the operational side of a week like this. EnterProtect backup keeps clean, restorable copies of client workloads, so a rebuild that goes wrong or a change that breaks a service does not leave the client without a recovery point.
Recovery gets a client running again after an incident, and EnterProtect vulnerability scanning gives you a standing view of exposure across client environments as part of routine service.
Frequently Asked Questions
What Is CVE-2026-126714?
CVE-2026-126714 is the identifier for a critical vulnerability in PHP's default file-based session handler. Google Cloud's bulletin GCP-2026-090 also names it phpAfterShell. The same bulletin lists the affected PHP versions and the Google Cloud services in scope.
Which PHP Versions Are Affected?
The bulletin lists PHP 8.5 (8.5.13), PHP 8.4 (8.4.28), PHP 8.3 (8.3.37) and PHP 8.2 (8.2.36). PHP 8.1 and PHP 7.2 are also listed as affected but are end of life, with no fix available. Clients on those end-of-life versions need to move to a supported runtime.
Does Disabling Session Upload Progress Fix the Problem?
Google Cloud says disabling Session Upload Progress in php.ini, with session.upload_progress.enabled = 0, mitigates the primary attack path for phpAfterShell in particular. That is a mitigation, not a patch. Where a supported patched runtime is available, upgrading is the durable fix.
Which Google Cloud Services Are Affected?
The bulletin names App Engine Standard (second-generation PHP 7.2 to 8.5 runtimes), App Engine Flexible, Cloud Run and Cloud Run functions. The mitigation notes also cover Cloud Run jobs and worker pools, and Cloud Functions (1st gen). Deployments pinned to a specific patch string are in scope too.
Can We Patch Self-managed Containers Ourselves?
Yes. The bulletin says Cloud Run containers and App Engine flexible custom runtimes can upgrade immediately to upstream PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13, then rebuild and redeploy. They do not have to wait for Google-managed runtime rollouts.
What Should We Do for Clients on End-of-Life PHP?
Treat it as a migration, not a patch. The bulletin states that no upstream patches will be released for PHP 8.1 or earlier, so PHP 7.2 and 8.1 clients need to move to a supported PHP runtime. Start with the clients whose PHP workloads are the most exposed.
Sources
- GCP-2026-090 (Google Cloud Security Corrected)