· via dev.to (home feed)
Drupal 10 end of life on December 9, 2026 ends security fixes; upgrade to Drupal 11 advised
Drupal 10 stops receiving releases and security fixes after December 9, 2026. A guide on dev.to explains how to check a site's version and plan the move to Drupal 11, which is supported until December 2028.

End of life arrives on December 9, 2026
Drupal 10 will reach end of life on December 9, 2026. According to a guide published on dev.to, which draws on Drupal's official release schedule, no further 10.x releases will ship after that date, security patches included. Sites running the platform will not stop working on the day itself — pages will keep loading as usual — but any vulnerability found after the cutoff will never be patched for Drupal 10.
The first week of December 2026 is crowded with milestones. Security support for Drupal 10.6, the final minor release of the 10.x branch, ends the week of December 7. Drupal 11.5 and Drupal 12.0 are both scheduled to ship in that same window. Drupal 11, the recommended destination for sites on Drupal 10 today, is supported until early December 2028, while Drupal 12 has a planned end of life in early December 2030.
The dev.to guide also flags a policy change: citing a November 2026 announcement from the Drupal Security Team, it reports that minor releases will be supported for 8 months rather than 12 starting in 2027. Teams on Drupal 11 will therefore need to keep pace with minors more often, and Drupal 11.4, the current minor, already has an announced end of support on April 21, 2027.
How to find out what a site is running
The guide lists three ways to check a site's version:
- The status report in the admin area, at Reports > Status report (the /admin/reports/status path), shows the exact version, such as 10.4.8. The guide calls this the most reliable method.
- Drupal adds an X-Generator HTTP header and a matching Generator meta tag to pages by default, revealing the major version. This exposes only the major number, and because modules can strip the header, its absence proves nothing.
- With file access, the version lives in the VERSION constant inside core/lib/Drupal.php, and developers can also read it through Composer or Drush.
Preparation first, then a Composer update
Moving from Drupal 10 to 11 is not a rebuild, the guide argues, but it does demand groundwork. The recommended sequence:
- Take a full backup of the database and files, confirm it actually restores, and rehearse on staging before touching production.
- Get to Drupal 10.3.0 or later first, since Drupal 11 can only be reached from that baseline — ideally 10.6.
- Sort out PHP. Drupal 11 requires PHP 8.3 or newer, with 11.3 and 11.4 also supporting 8.4 and 8.5. PHP 8.2 reaches its own end of life on December 31, 2026, so hosts still on 8.2 need to move regardless.
- Install the Upgrade Status module to flag contributed modules and custom code that are not Drupal 11 compatible, and use Drupal Rector to replace many deprecated calls automatically.
- Replace modules dropped from Drupal 11 core — Actions UI, Activity Tracker, Book, Forum, Statistics and Tour — by installing their contributed versions while still on Drupal 10.
- Run the upgrade itself with Composer, moving the core packages to version 11 with a dry run first, then applying database updates through Drush.
- Test key pages, forms and admin screens, confirm the status report shows a version 11 release, and uninstall Upgrade Status.
The official documentation covers extra cases the summary skips, such as write permissions on sites/default, a symfony/runtime plugin setting for Drupal 11.4, and what to do when drupal/core is required directly. The guide recommends following it line by line.
Drupal 11 is the safer target than Drupal 12
Although Drupal 12.0 lands the same week Drupal 10 dies, contributed modules typically need weeks or months to support a new major version. For sites on Drupal 10 today, the guide recommends Drupal 11: it is available, widely adopted and supported until December 2028, leaving roughly two years to prepare for Drupal 12 deliberately. There is also no direct path from Drupal 9 — those sites must pass through Drupal 10, at least version 10.3, first.
What to do if the deadline is missed
For sites that cannot upgrade in time — because a needed module lacks a Drupal 11 release, or a developer is unavailable — the guide recommends setting a realistic migration date and committing to it, staying on the very last Drupal 10.6 release, shrinking the attack surface with two-factor authentication on admin accounts and by uninstalling unused modules, and monitoring Drupal security advisories until the migration is done. An unsupported site is not compromised overnight, but each passing month raises the odds that a known flaw stays open.
Why it matters
End of life for a CMS means every future vulnerability becomes permanent until the site moves. With well under a month between mid-November 2026 and the December 9 cutoff, teams still on Drupal 10 face a compressed timeline, compounded by PHP 8.2's own end of life on December 31, 2026, which forces a hosting decision anyway. The shorter 8-month support window for minor releases starting in 2027 also turns upgrades into a routine discipline rather than an occasional project. The encouraging part, per the dev.to guide, is that the 10-to-11 move is fundamentally a prepared Composer update rather than a rebuild — provided module compatibility is checked and tested now rather than in a December rush.
- #drupal
- #php
- #content-management
- #security
- #software-upgrades