Drupal 10, Umbraco 13 and Kentico Xperience 13 all reach end of support within 22 days this December

Drupal 10 reaches end of life on 9 December 2026, Umbraco 13 LTS reaches its own five days later on 14 December, and Kentico Xperience 13 stops carrying vendor support of any kind after 31 December. The three dates fall within twenty-two days of each other.

Each of those dates is published by its own vendor and has been for months. An organisation on any one of the three shares its delivery window with everyone on the other two.

The arithmetic of how much of a Q4 window survives a change freeze is in our Drupal countdown post from 27 August. It works the same way for the other two dates, so this piece does not repeat it.

The three dates

Drupal 10 — 9 December 2026. End of life, with no further releases after that date, per the drupal.org core release schedule. Only the 10.6 branch carries security coverage until then, which means a site on 10.5 or earlier has already lost it. Drupal 12 is scheduled for the week of 7 December 2026, the same week Drupal 10’s support ends. The full version-by-version picture is on our Drupal end-of-life reference; /migrate/drupal is where to tell us what you are running.

Umbraco 13 LTS — 14 December 2026. Umbraco’s long-term support and end-of-life page lists that date as Umbraco 13’s end of life. The branch is in the last phase of its lifecycle now, which Umbraco describes as one where only security issues are fixed, running twelve months for an LTS major. After it, the page states the release is end of life and no longer recommended. /migrate/umbraco covers the move to Payload.

Kentico Xperience 13 — 31 December 2026. The Kentico product support lifecycle states that Xperience 13 carries security hotfixes only through 2026, and that all support, including security repairs, ceases from 1 January 2027. Of the three, this is the version with the least ambiguity about what stops and when. /migrate/kentico is the starting point.

Three deadlines, one Q4 delivery window

The reasoning from here is ours rather than anything the three vendors publish.

Upgrades and replatforms in this class are done by a small population of specialist agencies and system integrators, and the Drupal, Umbraco and .NET CMS practices overlap more than the platform boundaries suggest. Those firms are quoting the same autumn. Where a team plans to bring in outside help, the availability question is worth asking in September rather than in November, because it is the input least under the organisation’s own control.

The freeze calendars line up as well. The countdown post works through which sectors freeze when and why the tail of the calendar goes with it; this December, one freeze date sits in front of all three deadlines at once. An organisation running two of these platforms has a single usable window for both moves.

Budget is the third shared queue. Work that needs a Q4 approval is competing for the same committee slots as everything else being pushed to land before year-end, and the approval has to clear before the delivery work can start.

The three queues determine how much of the remaining time is available to spend. That is the number to plan against, and none of the three vendor dates states it.

Sitecore XP 10.0 and 10.1 hit a different kind of deadline

Sitecore XP 10.0 and 10.1 reach the end of Extended Support on 31 December 2026, the same day as Kentico Xperience 13. The shape is different: a Sustaining phase runs to 31 December 2028, and it excludes security updates. Under the support model in force since 1 June 2026, Sitecore also lists Extended Support security updates as chargeable, which we covered in what changed on 1 June.

We are keeping it out of the count above because “end of support” and “end of Extended Support, with a Sustaining phase that has no security updates in it” are different statements, and collapsing them would overstate three of the four dates. For a team on XP 10.0 or 10.1 the practical exposure from January still deserves the same place on the Q4 plan.

What is worth doing in the next two weeks

Confirm which version you are on and which of the published dates applies to it, since several of these platforms have branch-level distinctions that move the date. Find the start date of your own change freeze, which is the deadline that governs the work. Then get the move sized. The plan should be scoped, funded and dated before January.

Our CMS end-of-life page carries the current dates for Drupal, Sitecore, AEM, TYPO3, Kentico, Umbraco, Optimizely and Joomla, each sourced to the vendor’s own lifecycle page. A free consultation and a fixed quote come before any commitment, so putting a number against the work costs a conversation.

Between 9 and 31 December, three enterprise CMS versions stop receiving vendor support, and the organisations running them will be trying to book the same autumn.

FAQ

Which CMS versions reach end of life in December 2026? Three enterprise versions reach the end of vendor support inside the same month. Drupal 10 reaches end of life on 9 December 2026, per the drupal.org core release schedule. Umbraco 13 LTS reaches end of life on 14 December 2026, per the Umbraco long-term support and end-of-life page. Kentico Xperience 13 carries security hotfixes only through 2026, and all support including security repairs ceases from 1 January 2027, per the Kentico support lifecycle. Sitecore XP 10.0 and 10.1 also reach the end of Extended Support on 31 December 2026, which is a different kind of deadline: a Sustaining phase runs to 31 December 2028 and excludes security updates.

Is Drupal 10 supported after December 2026? No. Drupal 10 reaches end of life on 9 December 2026 and drupal.org publishes no releases for it after that date. Before then, only the 10.6 branch carries security coverage, so a site on 10.5 or earlier is already running without it. Drupal 12 is scheduled for the week of 7 December 2026, the same week Drupal 10’s support ends.

When does support for Umbraco 13 end? 14 December 2026. Umbraco publishes that date as Umbraco 13’s end of life on its long-term support and end-of-life page. Umbraco 13 is an LTS major, so its final lifecycle phase runs twelve months and fixes only security issues; after that phase the page states the release is end of life and no longer recommended. The date falls five days after Drupal 10’s.

What happens to Kentico Xperience 13 after 31 December 2026? Kentico’s support lifecycle states that Xperience 13 receives security hotfixes only through 2026, and that all support, including security repairs, ceases from 1 January 2027. That makes 31 December 2026 the last day the version has vendor coverage of any kind.

Can we move off one of these platforms before its December date? It depends on which of the two moves you mean, and on when your own change freeze starts rather than on the vendor date. An in-place upgrade to the next major can fit a Q4 window where the module or package compatibility work sizes up small. A replatform to a different CMS does not fit a window this short on an estate large enough to have been running the platform for years. Our view is that the achievable position by December is a supported branch plus a scoped and funded migration already running, which puts an end date on the exposure.

Sources

• Drupal core release schedule — the 9 December 2026 end-of-life date for Drupal 10, the 10.6 security branch, and the week of 7 December 2026 for Drupal 12
• Umbraco, long-term support and end-of-life — the 14 December 2026 end-of-life date for Umbraco 13, and the security-only final phase that runs twelve months for an LTS major
• Kentico product support lifecycle — security hotfixes through 2026 for Xperience 13, and all support ceasing from 1 January 2027
• Sitecore product support lifecycle (KB0641167) — the 31 December 2026 end of Extended Support for XP 10.0 and 10.1, the Sustaining phase to 31 December 2028, and the security-update line in the model in force since 1 June 2026
• WAYF, Drupal 10 ends 9 December, and for most teams the last date to ship a change is in November (27 August 2026) — the change-freeze arithmetic and the work-back checkpoints
• WAYF, CMS end-of-life dates — the full dated table, each row sourced to its vendor

The Q4 capacity reasoning, the agency-availability point and the two-week sequence in this piece are WAYF’s own planning view; none of the three vendors publishes this reasoning.