Skip to main content

Pantheon release notes

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

Action required
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 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 4, 2026

As part of Pantheon's Long-Term Support (LTS) for Drupal 7, Drupal 7.108 is now available with two security fixes.

  • Restored cache hardening: This release restores the DrupalCacheArray::__destruct() hardening from SA-CORE-2024-008 (CVE-2024-55638), which was lost in Drupal 7.103.
  • External authentication access bypass: This release fixes an access bypass caused by case-insensitive matching of external authentication names. Drupal now accepts only an exact match for names stored in the authmap table, and refuses new external logins whose name differs from an existing account only by case or trailing spaces.

Action required

Apply the latest upstream update to your Drupal 7 site to receive these fixes. See related documentation for how to apply core updates.

After you apply the update, run database updates in each environment, either from update.php or with Terminus:

This release includes the user_update_7021() database update, which makes the authmap.authname column case-sensitive on MySQL. The update stops without making changes if your authmap table contains names that differ only by case or trailing spaces. If that happens, merge or remove the duplicate entries, then run database updates again.

If your site uses an external authentication module, such as SAML, LDAP, or OpenID, and your identity provider treats names as case-insensitive, confirm that the provider sends names with consistent casing. Otherwise, affected users might see "Unable to log in. Contact the site administrator."

About Drupal 7 long-term support

Pantheon has partnered with Tag1 Consulting to deliver security updates and maintenance for Drupal 7 sites. This extended support is included at no additional cost.

For configuration guidance and detailed information, visit our related documentation.

November 3, 2026

The latest security update for Next.js addresses seven vulnerabilities: one high-severity and six medium-severity. Most of them affect applications that use specific features, such as Cache Components, Edge runtime routes, or image optimization.

Action required

Because this is a security update, we recommend that customers update affected Next.js applications as soon as possible. Customers are responsible for updating their application dependencies and redeploying; Pantheon does not update Next.js sites on customers' behalf.

The published Next.js advisories list 16.4.5 (Active LTS) and 15.5.29 (Maintenance LTS) as patched versions.

Highlights

This update addresses the following upstream security vulnerabilities. Severity labels are from the Next.js security release announcement.

  • High — Cross-tenant cache disclosure with unstable_cache and use cache: In applications with Cache Components enabled, a public use cache function that reads a root parameter, such as a tenant identifier, and is called both directly and from inside unstable_cache can return another request's result during a cold cache fill. See GHSA-mfr8-8qww-v76h.
  • Medium — Cross-root-parameter disclosure in nested use cache functions: With Cache Components, an outer cache entry can be stored before an inner function's root-parameter dependencies are recorded, which can disclose tenant-, site-, or locale-specific content. See GHSA-vc7v-qv4w-wrv8.
  • Medium — Shared shell cache poisoning in self-hosted applications: Self-hosted applications running next start with Cache Components enabled and Partial Prefetching disabled or unset can have request-specific values stored in a shared fallback shell through a crafted URL. See GHSA-vvgp-ww4w-46vf.
  • Medium — Cross-user cache disclosure through binary use cache arguments: Distinct binary arguments can produce the same cache identity, so applications that pass security-significant binary arguments through use cache and share entries across callers are affected. See GHSA-rhh4-g77r-r9qj.
  • Medium — Cross-client response injection in self-hosted applications: Applications that return an attacker-controlled fetched Response unchanged can mismatch compressed-response framing, which can be exploited behind an HTTP/1.1 reverse proxy that queues pipelined requests on a shared backend connection. See GHSA-pc58-hwjq-p385.
  • Medium — Cookie exposure through an internal header on Edge routes: App Router Edge Route Handlers and Pages Router Edge API routes that set cookies with NextResponse.cookies.set() expose the serialized cookie, including HttpOnly cookies, in the internal x-middleware-set-cookie response header. Exploitation requires attacker-controlled JavaScript on the same origin. See GHSA-f3mh-rxg3-f5g2.
  • Medium — SVG rejection bypass in image optimization: An attacker-controlled image from a permitted source can be misclassified as AVIF, bypassing images.dangerouslyAllowSVG: false when a native image backend that can decode SVG is in use. See GHSA-7qx7-33qx-rqx2.

Next.js 15.5.29 includes fixes for the cross-client response injection, Edge cookie exposure, and SVG rejection bypass issues. Next.js 16.4.5 includes fixes for all seven.

For full technical details and affected configurations, review the linked security advisories and the Next.js security release announcement.

October 28, 2026

The latest security release for WordPress, 7.1.4, is available on Pantheon.

Action required

Because this is a security update, we recommend all users upgrade to WordPress 7.1.4 as soon as possible from your Pantheon dashboard or Terminus to access the latest features, fixes, and security enhancements. See related documentation for how to apply core updates.

Pantheon has deployed platform-wide mitigations against external abuse of some of the vulnerabilities fixed in this release, and is actively monitoring those rules. However, customers need to update their sites as soon as possible.

Highlights

This release resolves 13 security issues:

  • A remote code execution weakness in the upgrade process.
  • Stored XSS via specially crafted block markup.
  • Stored XSS in privacy data removal requests.
  • Multiple stored XSS issues in the Interactivity API.
  • A stored denial of service in the Interactivity API.
  • Stored XSS in Customizer selective refresh.
  • Stored XSS in the Categories block.
  • Stored XSS in user login fields.
  • Unauthenticated disclosure of unpublished Customizer changesets.
  • Stored XSS in the Playlist and Image blocks.
  • Stored XSS in the Comments pagination blocks.
  • Notes readable by unauthorized privileged users, allowing privilege escalation.

This release also updates the bundled certificates to account for the revocation of an eMudhra root certificate.

For full details, see the WordPress 7.1.4 release announcement.

October 28, 2026

Pantheon has updated the default PHP version for the Drupal 7 upstream to PHP 8.3, replacing the previous default of PHP 8.2.

New Drupal 7 sites created from Pantheon's upstream use PHP 8.3. Existing Drupal 7 sites that do not set php_version in their own pantheon.yml move to PHP 8.3 when they apply this upstream update.

Action required

Test the update before you deploy it to the Live environment. Apply it in Dev or a Multidev environment, confirm your modules and theme work on PHP 8.3, then promote it.

If your Drupal 7 site needs to stay on PHP 8.2, pin the version by setting php_version: 8.2 in your site's pantheon.yml before you apply the update. For steps, see Manage PHP Versions.

If you maintain a custom upstream, this change is not reflected in your pantheon.upstream.yml unless you update your fork from Pantheon's upstream.