Blog

Drupal 10 loses support on 9 December 2026: what now?

Drupal 10 stops receiving security updates on 9 December 2026.

What that means in practice for your site, and by when you need to start the move to Drupal 11.


Einde van de support voor Drupal 10

What does 9 December 2026 mean in practice?

After 9 December there are no more security releases for Drupal 10, and contrib modules on that branch fall outside the security policy too.
Your site just keeps running, and that's the risk: nothing breaks on 10 December, so nothing reminds you.
Every vulnerability found after that date stays open on your version.

Drupal 12 is released in the week of 7 December 2026, the same week as Drupal 10's end of life.
Where things stand today:

Version Status on 12 September 2026
Drupal 7 Out of support since 5 January 2025
Drupal 8 Out of support since November 2021
Drupal 9 Out of support since November 2023
Drupal 10 End of life 9 December 2026, 10.6.0 is the last minor
Drupal 11 Current stable version, 11.4.x
Drupal 12 Expected in the week of 7 December 2026

How do you check which version you're running?

You'll see that in one minute on /admin/reports/status, the status report in your admin environment.
At the top is the exact core version number, below that your PHP version and the modules that are falling behind.
With server access, drush status shows the same thing, and composer show drupal/core-recommended shows what's locked in your project.

If you're on an older minor, updating to the latest Drupal 10 is the first job, because the upgrade to 11 starts from there.
Modules whose last release is years old already tell you where the time will go.

Persoon bekijkt met loep een statuspaneel met versieregels

The route is Drupal 11, not Drupal 12

The step from 10 to 11 is an update, not a rebuild.
Content, configuration and content types come along.
Five steps:

  1. Update to the latest Drupal 10 and the latest versions of your contrib modules, because those carry the compatibility.
  2. Run the Upgrade Status module: it reports per file what's not ready yet.
  3. Check your hosting.
    Drupal 11 needs a more recent PHP version and a newer Symfony generation.
  4. Clean up outdated code in your own modules and theme, using drupal-rector for the mechanical work.
  5. Upgrade on a separate branch, test on a copy of the production data, then plan a release moment.

What makes such a project expensive is almost never core itself.
It's the modules without a maintainer, custom code without tests and integrations nobody in-house still holds the key to.
Mapping that out takes about a day.
I do that work as Drupal migration and upgrade.

Still running Drupal 7, 8 or 9?

Then 9 December 2026 isn't your deadline, because you've been without support for longer already.
From the last Drupal 8 (8.9) or from Drupal 9, it stays an update: you go via 9 and 10 to 11, content and configuration come along.

Only from Drupal 7 is it a genuine rebuild: new platform, new theme, content moved over with the Migrate API.
A project of months.

On a Drupal 8 site, the work in practice sits mostly in contrib modules that never made the jump.
Otherwise, read what you need to do now with a Drupal 7 site.

What goes wrong if you do nothing?

The first thing that goes wrong isn't your website, it's your responsibility.
The site keeps running for months as if nothing's wrong, while four things start to slip.

  • Security: every vulnerability found after 9 December stays open, because there's no patch for your version.
  • Modules: maintainers aim their releases at 11 and later at 12, so you stop getting fixes.
  • Hosting: your hosting provider keeps moving PHP forward, and an outdated core can't keep up.
  • Compliance: for government, universities and enterprise, a core outside support is an audit problem too.
Kantelende websiteblokken met gebarsten schild en open slot

There's one more angle that's rarely included.
The European Accessibility Act, directive 2019/882, has applied since 28 June 2025, but not to every site.

It covers certain services, such as webshops, banking, transport and telecom, and works through national transposition, with exceptions for small businesses.
Whether it applies to you is a legal question you'd best have checked.

If your site falls under it, the technical work happens in your theme and components, with EN 301 549 and WCAG 2.2 level AA as the reference.
Doing that work on a core without updates means paying twice, so combine it with the accessibility work.
Also read whether the EAA applies to your website.

When do you need to start at the latest?

My rate is 75 to 95 euros per hour or 650 to 800 euros per day, excluding VAT, lower for long projects and returning clients.
What it costs you depends on your custom code, so an estimate follows after the status report and the Upgrade Status output.
The breakdown is on rates, and how that compares to the market you can read in what a freelance Drupal developer costs in 2026.

When you don't need to do anything about this

Two situations where I advise against an upgrade.
If you're replacing your site within the year anyway, you're better off rebuilding straight on 11, as a new platform.
And if you already have Drupal maintenance and support running, first check whether the major upgrade is already included in that contract.

Not sure where you stand? Send your version number and a short description via contact.
I'll look at your request and give you an honest picture of what's needed within 24 hours.

Frequently asked questions

When does support for Drupal 10 end?

Drupal 10 reaches end of life on 9 December 2026.
After that, no more security releases appear for core, and contrib modules on that branch fall outside the security policy.
Drupal 10.6.0 is the last minor release, so no new functionality will be added either.
Your site just keeps working, and that's what makes it deceptive: there's no visible moment when it goes wrong.

How do I see which Drupal version my website is running?

Log in and go to /admin/reports/status.
At the top of that status report is the exact version number of core, along with your PHP version and the modules that are behind.
With server access, drush status shows the same, and composer show drupal/core-recommended shows what's locked in your project.
If you see a 9 or a 7 there, the end of life of Drupal 10 isn't your first problem.

Is the step from Drupal 10 to Drupal 11 a migration or an update?

An update, provided you're on the latest Drupal 10.
Content, configuration and content types come along, you rebuild nothing.
The work sits in three things: contrib modules without a release for 11, outdated code in your own modules and theme, and hosting that provides a more recent PHP version.
From Drupal 8.9 or 9 onwards it stays an update, via 9 and 10 to 11.
Only from Drupal 7 is it a real migration, using the Migrate API.

Should I wait for Drupal 12?

No.
Drupal 12 comes out in the week of 7 December 2026, practically coinciding with the end of life of Drupal 10, and a new major doesn't have the full contrib ecosystem behind it on day one.
Go to Drupal 11, today's stable version on 11.4.x.
Keep your code free of deprecated API calls, and the later step to 12 is small work.

What does an upgrade to Drupal 11 cost?

That depends on your custom code and your modules, not on your number of pages.
I work at 75 to 95 euros per hour or 650 to 800 euros per day, excluding VAT.
For comparison: Belgian Drupal freelancers list rates on Malt between 400 and 600 euros per day, with a median around 550 euros.
A small, up-to-date site is a few days of work; with custom modules and integrations, a few weeks.

My site is still on Drupal 7. Is it too late to address that now?

It's not too late, but you won't make 9 December 2026 anymore.
Drupal 7 has been out of support since 5 January 2025, and the road to Drupal 11 from there is a rebuild of several months: new theme, new modules, content moved over with the Migrate API.
Start now and limit exposure in the meantime, because every month on a version without security updates is a month of extra risk.

A question about this topic?

Briefly describe your situation, and I'll let you know what's going on and what it would cost. No sales pitch.

Privacy policy
You can read how I handle your data in the privacy policy.

More to read