Pantheon incident
PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619
Resolved after 1 day 2 hours, affecting Customer Sites, on October 21, 2026.
Overnight monitoring continues to show persistent but limited probing, which is being blocked. Our rollout of updated PHP images across customer environments including LTS versions was complete as of 5pm Pacific time yesterday. We will continue to observe and may provide further analysis of our findings, but we are closing this incident.
Affected components
Update timeline
- investigating Oct 21, 2026, 02:03 PM UTC
Pantheon is actively mitigating against the PHP security vulnerabilities announced at 14:00 UTC today. PHP environments are being patched to the following versions: 8.5.12 8.4.27 8.3.36 8.2.35 Additionally, we are patching the following heirloom PHP branches via our LTS vendor: 8.1.x 8.0.x 7.4.x 7.3.x 7.2.x 7.1.x 7.0.x 5.6.x Finally, in preparation for this event, we pre-emptively deployed configuration changes to the runtime environment to mitigate potential attack vectors, and have implemented network-level mitigations to deflect attempted exploit payloads across the platform. No action is required from customers, as all available versions of PHP on Pantheon receive security updates through our LTS vendor. However, we continue to recommend that customers running on older versions of PHP that have reached End of Sale update to a version fully supported by the PHP community in order to minimize their overall risk. To pin your version of PHP to a different version, see https://docs.pantheon.io/guides/php/php-versions. We will update this post as patching progresses and as we learn more about the vulnerability.
- investigating Oct 21, 2026, 02:36 PM UTC
Updated PHP versions addressing CVE-2026-109618 and CVE-2026-109619 are now available, and we are beginning the process of rolling them out across our infrastructure. No action is required from customers. We will continue to update this post as the rollout progresses.
- investigating Oct 21, 2026, 04:07 PM UTC
Patching work is still in progress. Environments are being updated in stages, and protective mitigations remain active across the platform while the remaining updates complete. We are not yet seeing evidence of any volumetric exploit attempts. No customer action is needed. We will provide further updates as the rollout progresses.
- investigating Oct 21, 2026, 05:17 PM UTC
Patches continue rolling out across the infrastructure in stages, and protective mitigations remain active. We have not observed any volumetric exploit attempts, and no customer action is required.
- identified Oct 21, 2026, 06:22 PM UTC
Patching continues to roll out across the infrastructure in stages, with protective mitigations remaining active. We have not observed any volumetric exploit attempts, and no customer action is required. We expect to provide an estimated completion time for the patching rollout within the next hour.
- identified Oct 21, 2026, 07:30 PM UTC
We estimate the complete rollout for live environments on supported PHP versions (8.2 -> 8.5) within the next 20 minutes. We are also prioritizing pre-production environments for paying customers, and have preemptively patched development or mutli-dev environments that were toggled into a mutable code state (“SFTP mode”). We will provide an update on LTS versions of PHP (8.1.x through 5.6.x) once our upstream vendor has backported the patches and made updates available. That work has been in progress since 14:00 UTC. Our network-level mitigations remain effective, and are blocking a low but slowly increasing level of activity which is probing the vulnerable surface area. At this time we do not see evidence of widespread exploitation attempts, or any successful exploits. We will continue to deliver patched versions of PHP as quickly as possible, and maintain network level mitigation and continuous monitoring to provide our customers and the wider PHP community insights into how this situation plays out
- identified Oct 21, 2026, 07:49 PM UTC
We have patched all live production sites running supported PHP versions (8.2 - 8.5).
- identified Oct 21, 2026, 09:32 PM UTC
We have received LTS updates from our upstream vendor and are working to deploy the patch to older versions of PHP. We will post an update on that once it is complete or we have a clear ETA. Our network-level mitigations remain effective and we see no evidence of compromise for any sites on the platform.
- identified Oct 21, 2026, 10:13 PM UTC
Patched PHP builds are now available for all supported long-term support (LTS) PHP versions, and rollout to live environments running end-of-life PHP versions is underway. Live environments running fully supported PHP versions (8.2 and later) have already been patched.
- identified Oct 22, 2026, 12:16 AM UTC
We have completed patching production environments for all sites running LTS versions of PHP.
- identified Oct 22, 2026, 01:42 AM UTC
Patched PHP builds have been deployed to all LTS environments, all environments in SFTP mode, and all live environments running PHP 8.2 or later. Most paid non-live environments running PHP 8.2 or later are also patched. We expect the remaining rollout to continue over the next 24 to 48 hours.
- monitoring Oct 22, 2026, 02:08 AM UTC
We can now confirm that all pre-production customer environments are patched. Free/sandbox environments will be updated over the next 24-48 hours. Over the course of today, our network-level mitigations have blocked over 60,000 suspicious requests probing the vulnerability, and remain in place. This concludes our ongoing updates. We will share more analysis in the future based on what we can observe, but as of now, active mitigation work is complete.
- resolved Oct 22, 2026, 04:36 PM UTC
Overnight monitoring continues to show persistent but limited probing, which is being blocked. Our rollout of updated PHP images across customer environments including LTS versions was complete as of 5pm Pacific time yesterday. We will continue to observe and may provide further analysis of our findings, but we are closing this incident.
Your product runs on more than Pantheon
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.