Platform updatesDrupalPHP

Drupal 10 reaches end of life on 9 December. What support covers after that

Drupal 10 stops receiving releases on 9 December 2026, the same week Drupal 12 ships. Here is what end of life means for a live Drupal 10 site, why Drupal 11 is the right next step, and what a support team should be doing about it now.

WebsiteSupport.io Drupal Team10 Nov 2026 · 6 min read

Drupal 10 reaches end of life on 9 December 2026. After that date there will be no new Drupal 10 releases, including security releases. Drupal 10.6 is the last minor version, and Drupal 12 is due the same week. If your site is still on Drupal 10, there are about four weeks left in which a security advisory will still come with a Drupal 10 fix.

What end of life actually means

Your site will not stop working on 10 December. It will keep serving pages exactly as it does today. What changes is that when the Drupal Security Team next publishes a core advisory, there will be a patch for Drupal 11 and Drupal 12 but not for Drupal 10. Contributed modules will follow: maintainers drop Drupal 10 from new releases, so module security fixes also stop reaching you. The risk grows month by month rather than all at once.

Key dates

MilestoneDate
Drupal 10.5.x security supportEnded June 2026
Drupal 12.0 releaseWeek of 7 December 2026
Drupal 10 end of life (10.6.x)9 December 2026
PHP 8.2 end of life31 December 2026

The PHP date matters as much as the Drupal one. Plenty of Drupal 10 sites still run on PHP 8.1 or 8.2. PHP 8.1 is already unsupported and 8.2 follows at the end of December, so many sites face two end-of-life dates in the same month.

Drupal 11 now, not Drupal 12 later

It is tempting to skip a version and wait for Drupal 12. In practice that is not an option. There is no direct route from Drupal 10 to Drupal 12: a site has to be on Drupal 11.3 or later first. Drupal 12.0 will also be brand new in December, and many contributed modules will take months to declare support for it. Drupal 11 is mature, its module ecosystem is ready, and it is the version that keeps a Drupal 10 site patched.

What a Drupal 10 to 11 upgrade involves

For most well-maintained sites this is an upgrade, not a rebuild. Drupal 11 removed code that was deprecated during Drupal 10, so the work is in finding and fixing anything that still uses it. A typical upgrade runs like this:

  • Bring the site up to the latest Drupal 10.6 release and PHP 8.3 or newer, which Drupal 11 requires
  • Run the Upgrade Status module to list every contributed module, custom module and theme that is not yet Drupal 11 compatible
  • Update contributed modules to Drupal 11 compatible releases, and find replacements for any that have been abandoned
  • Fix deprecated API calls in custom code. Drupal Rector automates a large share of this
  • Lift version constraints in composer.json, upgrade core on a staging copy, and run the full regression test before go-live

What usually slows it down

Core is rarely the problem. The delays come from contributed modules with no Drupal 11 release, custom modules written against APIs that have since been removed, and hosting stacks that cannot move to PHP 8.3 quickly. An audit with Upgrade Status takes a day or two and tells you which of these applies to you. Do it first, so the upgrade can be scheduled with a realistic estimate.

If you cannot upgrade before 9 December

  • Make sure you are on the final Drupal 10.6 release and every contributed module is fully up to date before the deadline
  • Move to a supported PHP version, even if the Drupal upgrade has to wait
  • Watch each Wednesday core advisory closely after 9 December, and assess whether the flaw affects your site even without an official Drupal 10 patch
  • Put a date on the upgrade. A site that drifts on Drupal 10 for a year is much harder and more expensive to bring back

Upgrade, or rethink the site?

If the Upgrade Status report shows most of the site is custom code that would need rewriting, or the site no longer fits how your organisation works, a straight upgrade may not be the best use of the budget. That is the point to step back and plan a rebuild or a move to a different platform, which our sister agency London Design Works handles with a Migration Blueprint.

Still on Drupal 10?

For supported sites we treat the Drupal 10 to 11 upgrade as planned maintenance: a compatibility audit, module and custom code fixes, and an upgrade proved on staging before it goes live. If your current support doesn't cover it, we can start with the audit.

See Drupal support and maintenance →

Need a hand with your site?

Any CMS, any host. Our team in London and Surrey can take a look, usually the same day, and agree a fixed price before we start.

Get emergency help020 3608 2525

Stay ahead of the next release!

Security alerts, platform updates and industry analysis, straight to your inbox. Only essential updates.