Security Advisory Desk
unratedQCS priority 76/100Google Cloud

GCP-2026-090

A serious security flaw was found in PHP's way of saving session data when using file storage. This affects PHP versions from 7.2 up to 8.5, and impacts several Google Cloud products running PHP, such as App Engine and Cloud Run. An attacker who is not logged in could craft data to run harmful code on your server. To protect your applications right now, you can disable upload progress tracking if it's not needed, and consider changing session storage to use external services like Redis. Google is releasing updated PHP versions and patches for managed runtimes.

QCS published 21/11/2026, 8:51:49 am ISTVendor disclosure 21/11/2026, 5:35:07 am ISTVerified 22/11/2026, 2:29:00 am ISTRevision 1

In plain language

What this advisory means

A serious security flaw was found in PHP's way of saving session data when using file storage. This affects PHP versions from 7.2 up to 8.5, and impacts several Google Cloud products running PHP, such as App Engine and Cloud Run. An attacker who is not logged in could craft data to run harmful code on your server. To protect your applications right now, you can disable upload progress tracking if it's not needed, and consider changing session storage to use external services like Redis. Google is releasing updated PHP versions and patches for managed runtimes.

Technical explanation

How the issue affects the environment

CVE-2026-126714 is a critical vulnerability in PHP's default file-based session handler (session.save_handler= files). When PHP writes session data to disk—for example, during upload progress tracking—this write process is non-atomic. If the PHP process aborts mid-write due to memory limits or timeouts, it can leave a malformed session file on disk. Subsequent calls to session_start() deserialize this corrupted session data, enabling an unauthenticated remote attacker to craft input that triggers arbitrary code execution. This issue relates specifically to how session files are written, not to prior request-cleanup flaws. Immediate mitigation includes disabling session.upload_progress.enabled if upload progress tracking is unnecessary. Where possible, switching session storage from the local filesystem to external stores such as Redis, Memcache, or databases is also advised. Fixed PHP versions include 8.2.36, 8.3.37, 8.4.28, and 8.5.13. PHP 7.2 and 8.1 and earlier are end-of-life and have no patches available.

Operational impact

Why teams should care

This vulnerability could allow unauthenticated attackers to execute arbitrary code on affected PHP environments running on Google Cloud, potentially compromising application integrity, confidentiality, and availability. The impact is critical as attacker control can lead to full system compromise, data breach, or service disruption. Organizations using affected PHP versions on Google Cloud App Engine, Cloud Run, or Cloud Functions need to respond rapidly to mitigate risks until patched runtimes are deployed and applications are updated.

Immediate action

For self-managed containers (such as Cloud Run containers and App Engine flexible custom runtimes), upgrade immediately to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13, then rebuild and redeploy your applications. For managed runtimes with automatic base image updates enabled (App Engine Standard PHP 8.2-8.5 and Cloud Run services/functions), patched PHP runtimes will be deployed automatically. For managed runtimes without automatic updates, such as App Engine Flexible managed PHP runtime, Cloud Run jobs and worker pools, Cloud Functions (1st gen), and deployments pinned to specific patch versions, you must rebuild and redeploy once updated images are available. For older end-of-life versions (PHP 7.2 and 8.1), no official patches exist; upgrade to supported PHP versions or apply configuration mitigations. Immediate mitigations involve disabling session upload progress and migrating session storage away from file-based handlers.

Affected and fixed releases

Affected versionsPHP 8.5, PHP 8.4, PHP 8.3, PHP 8.2, PHP 8.1, PHP 7.2
Fixed versionsPHP 8.2.36, PHP 8.3.37, PHP 8.4.28, PHP 8.5.13

Temporary risk reduction

Disable PHP's session upload progress feature by setting session.upload_progress.enabled=0 in php.ini if your application does not require upload progress tracking. Additionally, configure PHP to use external session storage (such as Redis, Memcache, or a database) instead of file-based sessions by changing session.save_handler to the appropriate handler to prevent exploitation via malformed session files.

Evidence and validation checklist

  • Official Google Cloud Security Bulletin GCP-2026-090
  • Publication date: 2026-11-20
  • Description of vulnerability in PHP's default file-based session handler
  • Affected PHP versions and Google Cloud products listed
  • Remediation guidance for managed and self-managed environments
  • Mitigation recommendations for disabling session upload progress and using external session storage
  • Fixed PHP versions provided for supported releases
  • No fixes for end-of-life PHP 7.2 and 8.1 versions

Authoritative reference

Google Cloud Security Bulletins

QCS detected and normalized this record from the official source. Vendor guidance remains authoritative.

Open source