Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed

November 18, 2026

Pantheon now provides WordPress 7.1.5, a security release that fixes 20 issues in WordPress core.

Action required

Update your sites to WordPress 7.1.5 as soon as possible. Apply the update from your Pantheon dashboard or with Terminus. See how to apply core updates.

Pantheon deployed Web Application Firewall (WAF) protection in advance for some of the vulnerabilities this release fixes. The WAF rules do not replace the update, so update your sites as soon as possible.

This release fixes 20 security issues

Vulnerabilities that attackers can exploit without logging in:

  • Privilege escalation through Template Part block attributes, which could lead to remote code execution.
  • Stored cross-site scripting (XSS) through shortcode attributes in comments.
  • Denial of service through batched XML-RPC pingbacks.
  • Private taxonomy terms exposed through the REST API search endpoint.

Other vulnerabilities:

  • SQL injection in WP_Meta_Query through nested relation values.
  • SQL injection through the front page setting in Customizer changeset previews.
  • Privilege escalation from site Administrator to Super Admin on multisite through Customizer menu previews.
  • Stored XSS by users with the Contributor role or higher in the Comment Date block, in oEmbed provider responses, and in the block editor through media filenames.
  • Stored XSS by Administrators through Customizer previews.
  • XSS in wp_interactivity_data_wp_context() through the store namespace.
  • XSS in the block editor through Openverse image metadata.
  • Reflected XSS in the legacy media library popup.
  • Authorization bypass by users with the Author role or higher through comment editing in the admin.
  • User email addresses exposed to users with the Author role or higher through the REST API comments endpoint.
  • Information disclosure by users with the Editor role or higher through post and template author assignment in the REST API.
  • Information disclosure by Subscribers through XML-RPC wp.getComments.

Hardening changes:

  • WordPress now matches JSON media types with a corrected regular expression.
  • WordPress removes the block editor's Imgur embed variation, because its server-side provider no longer exists.

This release also removes 1024-bit certificates from the bundled root certificates in WordPress 6.9.12 and earlier. WordPress 7.0 already removed them.

Dependabot commits in the release history

The release history includes two commits that manage .github/dependabot.yml. Pantheon added them by mistake. The first commit adds the file and the next commit removes it, so applying the update makes no net change to your site.

For full details, see the WordPress 7.1.5 release announcement.

November 18, 2026

The Drupal Security Team released Drupal 10.6.22, 11.3.22, and 11.4.13 on November 18, 2026. These releases fix two security issues in Drupal core: SA-CORE-2026-017 and SA-CORE-2026-018. Pantheon also provides Drupal 7.109 for Drupal 7 sites through our LTS support with Tag1 Consulting.

Action required

Update your site to a fixed release as soon as possible:

  • Drupal 7: update to 7.109.
  • Drupal 10.x: update to 10.6.22.
  • Drupal 11.3.x: update to 11.3.22.
  • Drupal 11.4.x: update to 11.4.13.

Drupal 10 and 11 sites update core through Composer. To apply the update, use one-click core updates in the Pantheon dashboard.

Drupal 8, Drupal 9, Drupal 10.5.x and earlier, and Drupal 11.2.x and earlier have reached End of Life (EoL) and are not patched.

Pantheon deployed protections to all environments in advance as part of Drupal Steward, which mitigates SA-CORE-2026-017 (see below). We still advise you to update your sites as soon as possible.

Issues fixed

SA-CORE-2026-017: remote code execution

Drupal rates this issue critical (18/25), and it affects Drupal 10.x before 10.6.22, Drupal 11.0.0 and later before 11.3.22, and Drupal 11.4.0 and later before 11.4.13. Drupal tracks it as CVE-2026-132165.

Under specific conditions, an attacker can use the Drupal installer (install.php) to attempt to reinstall Drupal. This can lead to site takeover or remote code execution.

Pantheon's runtime now blocks the installer once the site is installed, in all environments.

SA-CORE-2026-018: gadget chain

Drupal rates this issue moderately critical (14/25), and it affects the same versions. Drupal tracks it as CVE-2026-132166.

Drupal core contains a chain of methods that could be exploitable if another vulnerability allows a site to deserialize untrusted data. The advisory states, "This issue is not directly exploitable."

Drupal 7

Pantheon now provides Drupal 7.109 through our LTS support for Drupal 7 with Tag1 Consulting. This core update removes install.php entirely. drush si continues to work. You need to apply the update to your site.

Apply the update from your Pantheon dashboard or with Terminus. See related documentation for how to apply core updates.

November 17, 2026

The Pantheon MCP Server now supports three more AI clients. You can connect them to operate on your Pantheon fleet through the same governed, user-authorized access introduced in the Pantheon MCP Server (Beta) release and expanded in Additional AI Client Support.

What's included

Pantheon MCP now supports these AI clients:

  • Gemini
  • Devin (formerly known as Windsurf)
  • Cursor

Authorization stays with Pantheon: the server forwards your own Pantheon identity, so an agent can only reach what you can already access.

Who it's for

Developers and teams who want to manage Pantheon sites and environments through the AI client they already use, while keeping control of what agents can change.

How to get started

Add the Pantheon MCP server in your preferred client and sign in with your normal Pantheon account. To disconnect and log out, remove the Pantheon MCP connection in your client.

For client-specific setup steps, see related documentation.

Availability

All Pantheon customers. For feedback, please sign up for the Pantheon Community Slack here. If you already have an account, join us in the #beta-mcp-server channel.

November 17, 2026

This release improves the Business Account dashboard, editing and localization workflows, MCP sign-in, and reliability across P1. It also includes updates to the P1 SDK and component packages.

Dashboard and Business Accounts

  • Content Publisher entries in the dashboard: Connected accounts, tokens, and Create collection are now only accessible from the user’s own Business Account. Previously, they were available everywhere which was confusing.
  • Clearer access-denied guidance: When you open a Site you are not authorized to access, the screen explains what to do next.
  • Less frequent logins needed: As you use the dashboard now you are less likely to be re-prompted to log in than you were previously. Using the dashboard refreshes the duration of your access.
  • Dashboard performance improvements: Previously the dashboard re-fetched data and fully reloaded pages more often than necessary. Recent updates to the dashboard improve this performance.

Editor, Workstreams, and localization

  • More accurate locale metadata: A localized page’s og:locale now reflects that page’s own locale. A page also cannot be assigned a locale already used by a linked page.
  • Locale-aware Site Structure: The locale filter shows each translation’s URL, with translations grouped under a locale badge.
  • MCP locale support: MCP clients can read and set a page’s locale.
  • Manage inherited redirects: Workstreams can now list, read, and edit redirects inherited from Live, even if those redirects were not created on the Workstream.

Developer updates

  • Updated P1 packages: p1-next-sdk, css-client, puck-css, and create-p1-starter-kit are at version 0.27.0.
  • Puck compatibility: puck-css and p1-next-sdk now require Puck 0.24.0 as a peer dependency. Existing projects should follow the Puck 0.24.0 migration guidance in the P1 Next.js SDK release notes.
  • Starter-kit compatibility: Projects using npm 10 on Node 22 can install successfully, and builds no longer print Next.js 16’s middleware deprecation warning on every run.

Reliability and performance

  • MCP authentication: A range of minor improvements that improves security and aligns with the authentication infrastructure for Pantheon's core platform's MCP.
  • Safer data operations: Workstream deletion, Structure creation and deletion, merge-job checkpoints, Site transfers, and template migration jobs now complete all-or-nothing.
  • More reliable editing and publishing: Concurrency issues affecting autosave, publish ordering, Structure node moves, and version-history repair have been addressed.
  • Smoother collaboration and account management: Concurrent user invitations and reopening a thread that already has an open context now return clear conflict responses rather than failing unexpectedly.
  • Faster redirect handling: Requests that do not match a redirect now use a more efficient lookup.
  • More efficient access checks: Agent Site permissions are batched, and Workstream access is resolved once per request in order to improve user experience.
November 16, 2026

Starting February 15, 2027, Pantheon will block Terminus versions that have reached end of life (EOL) from connecting to the platform. The initial affected versions are:

Terminus versionEOL dateBlocked starting
4.1.3February 2, 2027February 15, 2027
4.1.1January 29, 2027February 15, 2027
4.1.0November 4, 2026February 15, 2027
4.0.3September 29, 2026February 15, 2027
4.0.2September 11, 2026February 15, 2027
4.0.1September 5, 2026February 15, 2027
4.0.0May 19, 2026February 15, 2027
3.6.2May 7, 2026February 15, 2027
3.6.1March 03, 2026February 15, 2027
3.6.0 or earlierDecember 05, 2025February 15, 2027

Upcoming EOL and block dates for other versions

Versions still in support will be blocked on their EOL date. These dates have already been published and are unchanged:

Terminus versionEOL and block date
4.3.5November 9, 2027
4.3.4November 9, 2027
4.3.3November 3, 2027
4.3.2August 20, 2027
4.3.1June 23, 2027
4.3.0June 2, 2027
4.2.2May 26, 2027
4.2.1May 13, 2027
4.2.0April 30, 2027
4.1.9April 13, 2027
4.1.8April 8, 2027
4.1.7March 30, 2027
4.1.6March 23, 2027
4.1.4March 18, 2027

See Supported Terminus and PHP Versions for the current schedule.

Action required

Upgrade to the latest version of Terminus before February 15, 2027. To check which version you’re running, use terminus --version. For update steps on macOS (Homebrew), Windows and Linux (PHAR), see Install and Update Terminus.

If you are using Terminus in CI with GitHub Actions, we recommend using the Terminus GitHub Action, which always installs the latest version by default.

Why we're making this change

Pantheon set the EOL schedule for Terminus several years ago, but up until now has not enforced the requirement to use supported Terminus versions. Terminus runs on your computer or in your CI environment, so Pantheon can’t remove an old version. Customers who continue to use EOL versions of Terminus cause friction for security and support, as the interaction of some older versions with the platform can be unpredictable. Ensuring that Terminus clients in the field remain up to date will allow Pantheon to strengthen platform security and compliance, and evolve the platform more smoothly.

What happens when a version is blocked?

Commands run with a blocked Terminus version will fail to connect to Pantheon. Newer versions of Terminus will display a message asking you to upgrade. Older versions may not display the message, so automated processes, such as CI jobs, will simply fail until Terminus is upgraded.

What to expect going forward

  • Pantheon will announce each Terminus block at least 90 days in advance and will send reminders multiple times as the block date approaches.
  • Beginning with Terminus 4.3.5, each version will be supported for six months after the next version is released, down from one year. To prevent a newer version from reaching EOL before an older one, new versions will share the previous version's EOL date until the six-month window is reached. After that, the EOL date is the block date.
  • Dates already published are unchanged.
November 10, 2026

Starting Monday, November 16, 2026, Pantheon limits the retention period of manual backups to a maximum of 180 days. Requests for a longer retention period are rejected. This matches the retention options already available in the Site Dashboard, which offers 30 or 180 days.

If you create manual backups with Terminus, update to Terminus 4.3.5 before that date.

What is changing

  • Maximum retention: Manual backups can be retained for at most 180 days. Backup requests that ask for more are rejected.
  • terminus backup:create default: Before Terminus 4.3.5, terminus backup:create retained backups for 365 days when you did not pass --keep-for. Terminus 4.3.5 changes the default to 30 days, in line with the Site Dashboard.
  • Early validation in Terminus 4.3.5: terminus backup:create now checks --keep-for before contacting Pantheon. A value above 180, a value below 1, or a value that is not a whole number stops immediately with a message that explains the allowed range.

Automatic backups and backups created from the Site Dashboard are not affected.

What happens if you do not update

After November 16, 2026, older versions of Terminus still send the 365-day default. As a result:

  • terminus backup:create with no --keep-for option fails.
  • terminus backup:create with --keep-for set above 180 fails.

Scripts and CI pipelines that run terminus backup:create with the default arguments will fail until Terminus is updated.

Action required

  1. Update to Terminus 4.3.5 before November 16, 2026. See How to upgrade.
  2. Review any scripts or CI jobs that call terminus backup:create:
    • If they rely on the default retention, expect backups to be kept for 30 days instead of 365 days after you update.
    • If they pass --keep-for with a value above 180, lower it to 180 or less.

For example, to create a database backup that is retained for 90 days:

Learn more about creating backups.

How to upgrade Terminus

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

To confirm which version you are running:

If you have questions or concerns around Terminus, please use the Terminus issue queue.

November 10, 2026

Starting Tuesday, December 1, 2026, Pantheon is changing how it starts Next.js applications that use standalone output. If your build produces a standalone server, Pantheon runs that server directly instead of running npm run start. Your build is unchanged.

Why we're making this change

Standalone output is the deployment format Next.js recommends for containers. It contains only the files and dependencies your application needs at runtime. Running the standalone server directly starts your application faster.

Who is affected

Your site is affected only if next.config sets output: 'standalone'. Sites without standalone output continue to start with npm run start and need no changes.

Most affected sites also need no changes. Review your site if it does any of the following:

  • Runs setup in its start, prestart, or poststart script, such as preloading APM or OpenTelemetry, setting NODE_OPTIONS, running migrations, or starting a custom server. These scripts no longer run.
  • Reads files at runtime that Next.js build tracing doesn't detect, such as content directories, JSON data, or native binaries.
  • Builds file paths from process.cwd(). The standalone server runs from .next/standalone.
  • Reads server-side values from a committed .env file at runtime.

An affected site can start successfully but return errors when a page loads, so test your site after it next deploys.

Action required for affected sites

See Next.js Standalone Output on Pantheon for a fix for each case and steps to test standalone mode locally.

If you need more time, remove output: 'standalone' from next.config and Pantheon will continue to start your site with npm run start.

Rollout timeline

The change begins rolling out on Tuesday, December 1, 2026. Each environment picks up the change on its next deployment after the rollout reaches your site. Your runtime logs show Found Next.js standalone server at ... when the standalone server is in use.

For more details about how Pantheon builds and runs Next.js sites, see our build and runtime architecture.

Should you have any questions or concerns, please reach out to our customer support team via chat or email us at the Pantheon Helpdesk.

November 10, 2026

Terminus 4.3.5 is now available. This release points the Terminus account dashboard URL at the dashboard root and changes the default retention for backup:create to 30 days.

Key improvements in this release

  • Shorter default backup retention: backup:create now keeps backups for 30 days by default, previously 365. It also rejects --keep-for values above 180 days, below 1, or that are not whole numbers before contacting the API. The temporary backups created by local:getLiveDB and local:getLiveFiles also now default to 30 days. If your scripts or CI rely on the previous default, pass --keep-for explicitly. (#2934)
  • Account dashboard URL: The Terminus account dashboard URL now points at the dashboard root. (#2944)

How to upgrade to Terminus 4.3.5

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

For more information about this release, visit the GitHub release page.

If you have questions or concerns around Terminus, please use the Terminus issue queue.