Most Drupal teams assume they have time. They don't. Drupal 10 long-term support officially ends on December 9, 2026, and if your site is still running Drupal 10.5.x, you've already lost security coverage — that minor release went unsupported on June 17, 2026. We've been building and migrating Drupal sites since 2009, and we've seen this pattern before: teams wait, the window closes, and a planned upgrade turns into an emergency.
This post lays out exactly what the EOL timeline looks like, what your real options are, and how to avoid the trap of treating a deadline as a someday problem.
Key takeaways
- Drupal 10 long-term support ends December 9, 2026 — with no extensions expected
- Drupal 10.5.x already lost security support on June 17, 2026
- Drupal 10.6.x is the final Drupal 10 minor release — upgrade to it now if you haven't
- Teams must be on Drupal 11 (or plan for Drupal 12) before the December deadline
- Drupal 12.0.0 and Drupal 11.5.0 are both scheduled for the week of December 7, 2026
If you're weighing whether to handle this upgrade in-house or bring in help, see our Drupal development and migration services.
What the Drupal 10 EOL timeline actually looks like
The Drupal community publishes a core release schedule on drupal.org, and the dates are firm. Drupal 10.6.x is the final minor release in the Drupal 10 line. Security support for Drupal 10.6.x ends December 9, 2026 — the same week Drupal 12.0.0 and Drupal 11.5.0 are scheduled to ship. After that date, no security patches will be issued for any Drupal 10 release.
Here's what the final months look like in plain terms:
- June 17, 2026: Drupal 10.5.x loses security support. If you're still on 10.5.x, your site is already exposed.
- Week of June 22, 2026: Drupal 11.4.0 releases — the current stable path forward.
- Week of December 7, 2026: Drupal 12.0.0 and Drupal 11.5.0 both ship. Security support for Drupal 10.6.x and Drupal 11.3.x ends simultaneously.
- December 9, 2026: Drupal 10 end of life. No exceptions, no extended support.
If your team is still on Drupal 10.5.x today, you're not ahead of the deadline. You're already behind it.
For a deeper look at what drives that decision, see our post on whether you should update Drupal.
Should you upgrade to Drupal 11 or wait for Drupal 12?
This is the question we hear most often from existing clients, and the answer is almost always the same: upgrade to Drupal 11 now, don't wait for Drupal 12.
Here's why. Drupal 12.0.0 releases the week of December 7, 2026 — two days before Drupal 10 reaches EOL. That timeline gives teams almost no runway to evaluate Drupal 12, run compatibility audits on contrib modules, and complete a migration before the deadline. Betting on Drupal 12 as your exit strategy is a high-risk move.
Drupal 11 is stable, well-documented, and already supported through at least mid-2027 for the 11.4.x and 11.5.x lines. The upgrade path from Drupal 10 to Drupal 11 is the more predictable route, and most teams can complete it with a structured plan.
The teams that are struggling the most right now aren't the ones on large, complex Drupal installs. They're mid-size organizations on Drupal 10 with lightly maintained module sets — no dedicated Drupal developer on staff, a handful of custom modules nobody's touched in two years, and an assumption that the upgrade would be straightforward. It rarely is without an audit first.
What Drupal 11 actually requires from your codebase
The Drupal 11 upgrade isn't a one-click operation. Your site must meet specific prerequisites before you can move forward:
- PHP 8.3 minimum. If your hosting environment is still on PHP 8.1 or 8.2, you'll need to address that first.
- Contrib module compatibility. Not every module in the Drupal contrib ecosystem has a Drupal 11-compatible release. A thorough audit is required before you start the upgrade process.
- Symfony 7 dependency. Drupal 11 dropped support for older Symfony versions. Custom modules that depend on deprecated Symfony components will need updates.
- Deprecated API cleanup. Any custom code using deprecated Drupal 10 APIs must be updated. The Upgrade Status module on drupal.org is the right starting tool, but it won't catch everything.
We've run these audits on sites ranging from 10-module installs to platforms with 80+ contrib modules. The complexity scales quickly.
What happens if you miss the December 9, 2026 deadline?
Running an unsupported CMS isn't just a technical inconvenience. It's a business risk that compounds over time.
After December 9, 2026, any vulnerability discovered in Drupal 10 core will not receive a security advisory or patch from the Drupal Security Team. Your site remains exposed until you upgrade, and that exposure is public knowledge — the security community tracks EOL software closely.
For regulated industries — healthcare, government, financial services — running unsupported software creates compliance exposure that your legal and security teams will not want to explain to an auditor.
How to build your Drupal upgrade plan before the deadline
A Drupal 10 to Drupal 11 upgrade done well follows a predictable structure. Here's how we approach it:
Step 1: Run a compatibility audit
Before writing a single line of code, map your current state. Document every contrib module, its Drupal 11 compatibility status, and whether an alternative exists if the module is abandoned. The Upgrade Status module gives you a starting point, but manual review of custom modules is essential.
Step 2: Resolve your PHP version
Confirm your hosting environment can run PHP 8.3. If it can't, plan that infrastructure change in parallel with the code audit — don't let it become a last-minute blocker.
Step 3: Update contrib modules
Don't attempt a core upgrade before your contrib ecosystem is ready. Update modules to their latest Drupal 10-compatible releases first, then move to Drupal 11-compatible versions. Doing this incrementally reduces risk.
Step 4: Upgrade core in a staging environment
Never test a major version upgrade in production. Run the upgrade in a staged environment, execute your full regression test suite, and document what breaks. Plan for at least one round of fixes before you're ready to promote to production.
Step 5: Set your go-live date before October 2026
December 7 is when Drupal 12 ships and Drupal 10 security coverage ends. If your go-live is in that same week, you have no buffer. Target a production upgrade no later than October 2026 to allow for post-launch stabilization.
The case for acting now, not in Q4 2026
The Drupal ecosystem has a well-documented history of EOL deadline pressure. Drupal 7 end of life was extended multiple times, and many teams treated that as a template for future deadlines. Drupal 10 will not follow that pattern. The Drupal Association has structured the release cycle around clear, fixed dates, and the December 9, 2026 date is published and firm.
Teams that start their Drupal 11 upgrade planning in mid-2026 will have comfortable timelines and options. Teams that wait until Q4 2026 will be competing for limited Drupal developer capacity during the highest-demand period in the ecosystem's near-term history. Rates go up. Timelines compress. Mistakes happen under deadline pressure.
WeKnow has been contributing to Drupal since 2009 and is the number one Drupal contributor in Latin America. If your team is looking at this deadline and trying to figure out where to start, we're worth a conversation.
Frequently asked questions
What is Drupal 10's long-term support end date?
Drupal 10 long-term support ends on December 9, 2026, as confirmed on the drupal.org core release schedule. After that date, no security patches will be issued for any Drupal 10 release. Drupal 10.6.x is the only Drupal 10 minor version still receiving security coverage through that date.
Can I skip Drupal 11 and upgrade directly to Drupal 12?
Technically possible, but not advisable for most teams. Drupal 12.0.0 releases the week of December 7, 2026 — two days before Drupal 10 EOL. There's no realistic window to evaluate Drupal 12 compatibility and complete a migration before the deadline. Drupal 11 is the practical upgrade path now.
How long does a Drupal 10 to Drupal 11 upgrade typically take?
Timeline depends heavily on your contrib module count, the state of your custom code, and your PHP version. Sites with clean codebases and well-maintained module sets can move through the upgrade in 4-8 weeks. Complex installs with custom modules and legacy PHP versions often require 3-5 months of structured work, including audit, remediation, and testing.
Closing
Drupal 10 long-term support ends in December 2026, and the runway is shorter than it looks. If you're on Drupal 10.5.x, you're already outside the security perimeter. If you're on Drupal 10.6.x and haven't started planning your Drupal 11 upgrade, the time to start is now — not when the deadline appears on your calendar.
The teams that handle this well are the ones that run the audit early, resolve their contrib dependencies before they become blockers, and get to production before Q4 pressure sets in.
If you want to talk through your Drupal roadmap with a team that's been doing this since Drupal 6, reach out at yes@weknowinc.com. We're not going to pitch you a package — we'll tell you what we'd actually do with your specific setup.