Is Pantheon down?

RESOLVED: PHP CVE-2026-115560 mitigation Pantheon is aware of the release of CVE-2026-115560 from PHP.net; the recommended remediations for this vulnerability were already in place prior to the announcement. No action is required.

We are investigating an issue affecting environment creation. Customers may be unable to create new Drupal or WordPress sites, test environments, or Multidev environments through the Dashboard or Terminus. In some cases, an environment may appear in the environment list but return an error when accessed. Engineering is investigating the underlying provisioning issue. We will provide another update as more information becomes available.

A fix has been implemented for the environment creation issue, and we are monitoring the results. Customers should see creation of new Drupal and WordPress sites, test environments, and Multidev environments through the Dashboard and Terminus return to normal. We are continuing to verify successful environment creation and will provide another update once monitoring is complete.

The environment creation issue has been resolved. Creation of new Drupal and WordPress sites, test environments, and Multidev environments through the Dashboard and Terminus has returned to normal. Monitoring is complete, and environment creation is operating as expected.

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.

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.

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.

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.

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.

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

We have patched all live production sites running supported PHP versions (8.2 - 8.5).

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.

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.

We have completed patching production environments for all sites running LTS versions of PHP.

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.

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.

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.

We have identified an issue affecting only Terminus workflows and commands, including Terminus authentication and API requests. Some Terminus requests may fail or time out. Our Engineering team is working to restore Terminus service. There is currently no confirmed workaround or estimated time to resolution. The Pantheon Dashboard and sites remain unaffected. If you need immediate assistance, please open a chat with our Support bot and request an urgent Support ticket, or email [email protected] for direct assistance.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A Drupal core security release is now available for CVE-2026-108097 (risk 19/25). It fixes a critical remote code execution vulnerability in the Field UI module. Drupal core alone is not directly exploitable, but several exploit paths exist through contributed modules, including at least one path that does not require authentication. Custom code can also expose the vulnerable functionality. Action required Update your Drupal sites to a patched release as soon as possible: Drupal 11.4.10Drupal 11.3.19Drupal 10.6.19 Drupal 12.0.0-alpha1 through 12.0.0-beta1 are also affected. See the Drupal security advisory for Drupal 12 remediation details. Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, Drupal 9, and Drupal 8.9 are end-of-life. These versions are affected and do not receive security patches. Upgrade sites on these versions to a supported Drupal release. To apply the update, use the Drupal core update workflow in the Pantheon Dashboard. See the Pantheon security release note for instructions. Mitigation until you update If you cannot update immediately, uninstall the core Field UI module (field_ui). The Drupal Security Team states that this protects your site until you update. As a founding Platform Partner of the Drupal Steward program, Pantheon provides protection against some known attack vectors. Drupal Steward does not cover all possible exploits, so it does not replace updating your site.

We are aware of the Drupal 7 release and will update this incident when it is available as an upstream update.

Drupal 7.107 is now available as an upstream update. Customers running Drupal 7 applications should update to Drupal 7.107 as soon as possible. To apply the update, use the Drupal core update workflow in the Pantheon Dashboard.

Drupal 10 and 11 security updates are available through Integrated Composer, and the Drupal 7.107 upstream security update has been released. Release notes are available for both update paths: Drupal core security update and Drupal 7.107 security update.

Drupal Steward protection is in place for some known attack vectors related to CVE-2026-108097. This reduces exposure, but does not cover every possible exploit path or replace applying the security update. No customer impact is currently reported, and we continue to monitor. Patched Drupal 10 and 11 releases are available through Integrated Composer, and Drupal 7.107 is available as an upstream update. Please update affected sites as soon as possible. If you cannot update immediately, uninstall the core Field UI module (field_ui) as a temporary mitigation. See the Drupal core security update and Drupal 7.107 security update for details.