Tech

Drupal 10 Reaches End of Life: What It Means and What to Do Next

8 min read

Book One-Time Free Consultation
Drupal 10 Reaches End of Life: What It Means and What to Do Next
Tech

If your website is running on Drupal 10, there's a date you need to have on your radar: 9 December 2026. That's when Drupal 10 officially reaches end of life, and when the Drupal security team stops issuing patches and advisories for it. After that date, your site keeps running, but it's on its own.

It’s not just something to think about in the future, because Drupal 10.4.x was out of support from December 2025, and Drupal 10.5.x went out of security support from June 2026, meaning that many sites on Drupal 10 are already operating with no security support at all. There is no time to lose in preparing for the EOL, which is why at Dotsquares we help our clients manage these migrations properly. Let’s take a look at what’s going on.

What Does "End of Life" Actually Mean for Your Drupal 10 Site?

The end of life, per the core release schedule of Drupal, is when the Drupal security team officially stops looking out for vulnerabilities in Drupal 10 core or releases patches for any of them. The site will continue to work, with pages being rendered, user logging in, and publishing content. It is only that any vulnerabilities found from 2026 onwards will not be patched.

That's a bigger risk than it might sound. After Drupal 7 reached end of life, data from HeroDevs showed that two to six high-severity vulnerabilities per month appeared in popular contributed modules in the first year alone. The same pattern is likely to follow for Drupal 10. Without official security releases, those vulnerabilities stay open.

Then there is the issue of compliance. For example, compliance standards such as PCI DSS, HIPAA, GDPR, and SOC 2 mandate that organizations operate on software that is supported and regularly patched. Operating on end-of-life CMS puts the company at risk for compliance failures.

Key EOL dates to know:

Drupal 10.4.x - unsupported since December 2025

Drupal 10.5.x - security support ended June 2026

Drupal 10.6.x - final supported minor version, security ends 9 December 2026

Drupal 12 - scheduled for release the same week: 7 December 2026

Why Drupal 11 Is the Right Move, and What It Brings

The Drupal 11 came out on 2 August 2024 and at the moment, it is the current and supported version of Drupal, which is supported until early December 2028. In accordance with the Drupal core release cycle, the support period of any major version lasts for four to four and a half years; therefore, there is plenty of time for Drupal 11. It is not a revolutionary change in architecture as it continues the previous version, Drupal 10, hence, it will be much easier to update compared to other major versions.

What does Drupal 11 actually change? The headline improvements include:

  • PHP 8.3 as the minimum requirement - better performance, improved type safety, and access to modern language features
  • Updated database requirements - MySQL 8.0+, MariaDB 10.6+, or PostgreSQL 16
  • Removed legacy core modules - Actions UI, Activity Tracker, Book, Forum, Statistics, and Tour have been dropped from core; each needs a contributed equivalent or removal
  • Cleaner codebase - deprecated APIs from Drupal 10 have been removed, reducing technical debt
  • Refreshed admin interface and editorial tools - improved usability for content teams
  • Stronger accessibility compliance and improved caching for better frontend performance

Crucially, Drupal 11.0.0 shares its public APIs with Drupal 10.3+. If your site is already on a recent minor version of Drupal 10 and your contributed modules have Drupal 11 compatibility, the upgrade is a relatively clean process. The bigger lift comes from custom code and any modules that haven't yet released Drupal 11-compatible versions.

It's also worth noting that Drupal 10 cannot jump directly to Drupal 12; the upgrade path goes Drupal 10 → Drupal 11 → Drupal 12. Getting to Drupal 11 now means you're in the right position for whatever comes next.

How to Upgrade from Drupal 10 to Drupal 11 - Step by Step

As The Drop Times reports, organisations are being urged to start planning staged upgrades now, not in autumn 2026. The upgrade isn't something to bolt on at the last minute. If you're running a large site with custom modules, contributed modules, and significant content, the process needs runway, ideally starting now rather than in Q4 2026.

Step 1 - Check Which Minor Version You're On

Run drush status or check the Status Report in Drupal's admin. If you're on 10.4.x or 10.5.x, your first priority is updating to 10.6.x to regain active security coverage while you plan the full upgrade to Drupal 11.

Step 2 - Run the Upgrade Status Module

The Upgrade Status module scans your contributed and custom modules for Drupal 11 compatibility and flags deprecated code. Running this early gives you a clear picture of the work involved and helps prioritise which modules need attention first.

Step 3 - Audit Your Contributed Modules

Check whether the modules your site depends on have officially released Drupal 11-compatible versions. For modules that haven't, the Lenient Composer Plugin can allow installation in some cases, but that's a temporary workaround, not a long-term solution. Modules without active Drupal 11 support may need replacing.

Step 4 - Confirm Infrastructure Requirements

Drupal 11 requires PHP 8.3 or higher and updated database versions. For many teams, getting sign-off on infrastructure changes takes longer than the development work itself, so this conversation needs to happen early. Dotsquares can support both the technical assessment and the conversation with hosting providers if needed.

Step 5 - Test in a Staging Environment

Before anything touches production, run the full upgrade in an isolated environment. Test all custom functionality, integrations, and editor workflows. This is where issues surface, not on the live site.

Step 6 - Set a Deadline Well Before 9 December 2026

Give yourself a buffer. Aiming for a November 2026 go-live date leaves room to handle unexpected issues without racing the official EOL cutoff. If you're on 10.5.x or below, the urgency is even higher; you're already without security support.

What Happens If You Don't Upgrade?

However, some teams may opt to postpone; the site functions fine, upgrading it costs money, and 2026 looks far away now. Yet, the number of problems related to staying on an unsupported platform starts to accumulate fast.

Security holes in core and contributed modules won’t get patched, which increases the exposure period with each month that goes by post-EOL. Auditors from the compliance department at companies subject to any kind of personal data or payment security regulation will note that they work with unsupported software. The longer the postponement is, the greater the distance between the existing Drupal 10 site code and Drupal 11 becomes, thus complicating and costing the upgrade process more than necessary.

The truth of the matter is that Drupal 11 is a robust and supported platform with almost two years’ worth of patches in place. The upgrade process from the most recent Drupal 10 version is well-documented and manageable with proper support.

How Dotsquares Can Help

Dotsquares is a Drupal Silver Partner with a dedicated Drupal development team that has worked on Drupal projects across e-commerce, enterprise CMS, and complex multi-site setups. Our Drupal development services cover the full upgrade lifecycle, from compatibility audits and infrastructure planning through to migration execution, testing and post-launch support.

We also offer Drupal Acquia CMS implementation through our Drupal Acquia CMS service, for organisations looking to move to a managed, enterprise-grade Drupal environment as part of this transition. And for teams looking at the broader picture beyond this upgrade cycle, our CMS development services cover architecture decisions, platform selection, and long-term digital roadmaps.

If you're unsure where your site currently sits in the Drupal 10 support window, or what an upgrade would involve, the right starting point is a conversation. The earlier that happens, the more options you have.

FAQs

When does Drupal 10 reach end of life?

The official end-of-life for Drupal 10 is 9 December 2026, coinciding with the launch of Drupal 12. Past this point, the Drupal Security Team will cease releasing any patches or advisories related to Drupal 10 core. Remember that Drupal 10.4.x reached its end of life in December 2025, and 10.5.x reached it in June 2026.

Can I upgrade directly from Drupal 10 to Drupal 12?

No. It is mandatory to upgrade Drupal through each major version in order. You have to upgrade from Drupal 10 to Drupal 11 first and then upgrade from Drupal 11 to Drupal 12 after it becomes available. Migrating to Drupal 11 is the only correct way to proceed.

What are the minimum requirements for Drupal 11?

Drupal 11 is compatible with PHP 8.3 and above, MySQL 8.0 and above or MariaDB 10.6 and above, and PostgreSQL 16 if Postgres is used. Your site needs to be on Drupal 10.3 or newer before upgrading. It often takes a long lead time to prepare the infrastructure, so you should verify these requirements early on.

What risks does running an end-of-life Drupal version create?

With the end of life for the version, security flaws in the Drupal core and contributed modules remain unpatched. It leads to an increasing exposure window for your website. If you operate under any of the compliance requirements (PCI DSS, HIPAA, or GDPR), running unsupported software could lead to audit issues for you.

How long does a Drupal 10 to Drupal 11 upgrade take?

The timeline differs greatly depending on the particular situation. A maintained website using a newer 10.x minor release with compatible modules can be upgraded in a week or two. Websites that have custom code or require incompatible contributed modules and even additional infrastructure might need several months to do the job. Early start maximises your options.

Planning a Drupal 10 to Drupal 11 Migration?

Dotsquares has helped businesses navigate Drupal upgrades across a wide range of scales and complexity levels. Whether you need a full migration plan, a module compatibility audit, or hands-on development support, we can help you get there before the December 2026 deadline.

Talk to Our Drupal Team

Follow Usfacebookx-twitterlinkedin

Related Post

Article Image
calendar-icon November 17, 2026
Tech

Drupal 10 Reaches End of Life: What It Means and What to Do Next

Drupal 10 reaches end of life on 9 December 2026. Learn about security risks, Drupal 11 benefits, and the steps to upgrade.

Keep Reading
Article Image
calendar-icon November 17, 2026
Tech

Best AI Model Optimisation Techniques to Improve Speed, Accuracy and Efficiency

Explore the best AI model optimisation techniques to improve speed, accuracy and efficiency, reduce inference costs, and prepare models for reliable business deployment.

Keep Reading
Article Image
calendar-icon November 17, 2026
Tech

How to Build an AI Personal Finance App: Features, Tech Stack and Cost

Learn how to build an AI personal finance app, including key features, AI capabilities, tech stack, bank data integration, development costs and MVP planning.

Keep Reading

Is Your Business AI-Ready?

sidebar