Buscar Servicios con IA

Describe el servicio que necesitas

O prueba con uno de estos ejemplos:

Back to blog

Drupal Security Support: From Twelve to Eight Months

Share
Aircraft technician next to a plane with the Drupal logo: Drupal security support moves to eight months per version.

On November 2, 2026, the Drupal Security Team announced a change to Drupal security support: starting in 2027, each minor version of core will be covered for eight months instead of twelve. Drupal 11 is still supported until December 2028, but staying on the same minor version for a year will no longer be safe. In this article, we explain what changed, why, and how to plan site maintenance under the new schedule.

Major and minor versions: the difference that matters

Drupal numbers its versions with two figures. The first is the major version (10, 11, 12) and the second is the minor version (11.3, 11.4). Minor versions come out every six months: 11.3 was released in December 2025 and 11.4 in June 2026. They bring improvements and fixes without breaking site compatibility.

The announced change only affects minor versions. Major versions still get at least four years of support:

Major versionSupported until
Drupal 10 (released December 2022)December 2026
Drupal 11 (released August 2024)December 2028
Drupal 12 (scheduled for December 2026)December 2030

What changes in Drupal security support from 2027

Since Drupal 8.6, in 2018, each minor version was supported for twelve months. From 2027, it will be supported for eight: six months of bug fixes followed by two months of security-only fixes. The exception is the final minor version of each major version, which will get six months of bug fixes and six months of security support.

This is the schedule published in the announcement:

Minor versionReleaseSecurity support until
11.3December 2025December 2026
11.4June 2026April 2027 (transition period)
12.0 and 11.5Scheduled for December 2026August 2027
12.1 and 11.6Scheduled for June 2027February 2028

In practice, the window to update shrinks from six months to two.

Under the previous model, when a new minor version came out, the previous one kept six months of support. Under the new one, it has about two months left. A site that does not update in time is left without security fixes, even if its major version is still supported.

Why Drupal made this decision

According to the announcement, Drupal, like all open source projects, is receiving a flood of security reports driven by the widespread use of AI tools, and its security team cannot sustain that volume with current funding. The risk for site owners was that security fixes would take longer to ship.

According to the Drupal Security Team, with fewer versions supported at the same time, the work of backporting each security fix to older versions drops by 30%. The change also aligns Drupal with Symfony, the PHP framework whose components Drupal uses and whose standard releases also receive eight months of maintenance.

The Drop Times adds context: on October 28, core release manager Jess Myrbo (xjm) reported that funding for core stability and security is at its lowest level since 2012.

What it means for Colombia and for our clients

  • Updating is no longer an occasional project. A Drupal site will need two minor-version updates per year. It is worth including them from the start in the budget and in the support contract.
  • Every update needs testing. Contributed modules, custom themes and integrations must work with the new version. Two months is enough only if that process is defined in advance.
  • Public institutions should review their contracts. If support is contracted on an annual basis and covers a single update, it is no longer enough.
  • Drupal 10 has a closer deadline. Its support ends in December 2026. We explain it in our article on the December 2026 end of support.

What to do now

  • Check the minor version of each site. It appears in the Drupal status report (Reports → Status report).
  • If you are on Drupal 11.3, update to 11.4 or later before December 2026. If you are on 11.4, plan the update before April 2027.
  • If you are on Drupal 10, plan the migration to Drupal 11 as soon as possible.
  • Set a fixed schedule: two update windows per year, within two months of each June and December release.
  • Review your contract with your hosting or support provider and confirm whether it includes minor-version updates.

The role of managed hosting

With shorter cycles, a site’s security depends more and more on someone watching the schedule and applying updates on time. It is the kind of task a managed hosting service can take on, such as SeedCloud, Seedem’s managed infrastructure for Drupal sites.

If you are not sure which minor version your site is on or how much time it has left, Seedem can review it with you. Contact us.

Sources

  • Drupal Security Team – PSA-2026-11-02: Security support for Drupal core minor versions reduced to 8 months
  • The Drop Times – Drupal Cuts Minor-Release Security Support to Eight Months