EOL calendar: when your software stops getting security updates

Linux distributions, PHP, Node.js, Java, Python, databases and frameworks all stop getting security updates at some point. The calendar shows when, and every entry links to the vendor’s source.

The dates

As of: ·soon means within the next 6 months ·All dates as a calendar (.ics)

2026

  1. MySQL 8.0: end of life

    Extension: Oracle Sustaining Support only

    Source: mysql.com · Databases

    ended
  2. Node.js 20: end of life

    Extension: commercial extended support (HeroDevs, TuxCare), no public end date

    Source: github.com · Runtimes

    ended
  3. TYPO3 v12: security support ends

    Extension: TYPO3 ELTS until 30 Apr 2030

    Source: get.typo3.org · Frameworks & CMS

    ended
  4. MariaDB 10.6 (community): end of life

    Extension: MariaDB Enterprise until 23 Aug 2028

    Source: mariadb.org · Databases

    ended
  5. Debian 12 "bookworm": standard support ends

    Extension: Debian LTS until 30 Jun 2028

    Source: debian.org · Operating systems

    ended
  6. Debian 11 "bullseye" (LTS): end of life

    Extension: Freexian ELTS until 30 Jun 2031

    Source: debian.org · Operating systems

    ended
  7. OpenSSL 3.0: end of life

    Extension: OpenSSL premium support, no public end date

    Source: openssl-library.org · Runtimes

    ended
  8. Python 3.10: end of life

    Source: devguide.python.org · Runtimes

    ended
  9. PostgreSQL 14: end of life

    Source: postgresql.org · Databases

    soon
  10. Drupal 10: end of life

    Source: drupal.org · Frameworks & CMS

    soon
  11. PHP 8.2: security support ends

    Extension: Zend PHP LTS, TuxCare, distribution backports

    Source: php.net · Runtimes

    soon

2027

  1. Laravel 12: security support ends

    Source: laravel.com · Frameworks & CMS

    soon
  2. Redis OSS 6.2: end of life

    Source: redis.io · Databases

    soon
  3. Node.js 22: end of life

    Source: github.com · Runtimes

    later
  4. TYPO3 v10 (ELTS): end of life

    ELTS is booked per year. The date is the latest possible end.

    Source: typo3.com · Frameworks & CMS

    later
  5. Ubuntu 22.04 LTS: standard support ends

    Extension: Ubuntu Pro ESM until May 2032

    Canonical's release cycle page says May 2027, its release team list says June 2027. We check this monthly.

    Source: ubuntu.com · Operating systems

    later
  6. RHEL 9, AlmaLinux 9, Rocky Linux 9: full support ends

    Extension: security updates (maintenance support) until 31 May 2032

    Not an end of life: only new features and hardware enablement stop, security updates continue.

    Source: access.redhat.com · Operating systems

    later
  7. CentOS Stream 9: end of life

    Source: centos.org · Operating systems

    later
  8. MongoDB 7.0: end of life

    Source: mongodb.com · Databases

    later
  9. TYPO3 v13: security support ends

    Extension: TYPO3 ELTS, end date not yet published

    Source: typo3.com · Frameworks & CMS

    later
  10. Python 3.11: end of life

    Scheduled date, it can move.

    Source: devguide.python.org · Runtimes

    later
  11. Eclipse Temurin 11, 17: end of life

    Adoptium says support lasts at least until October 2027.

    Source: adoptium.net · Runtimes

    later
  12. PostgreSQL 15: end of life

    Source: postgresql.org · Databases

    later
  13. Symfony 6.4: security support ends

    Source: symfony.com · Frameworks & CMS

    later
  14. PHP 8.3: security support ends

    Source: php.net · Runtimes

    later

2028

  1. MariaDB 10.11: end of life

    Source: mariadb.org · Databases

    later
  2. Node.js 24: end of life

    Source: github.com · Runtimes

    later
  3. Ubuntu 18.04 (Pro ESM): end of life

    Extension: Ubuntu Pro Legacy until May 2033

    Source: ubuntu.com · Operating systems

    later
  4. Debian 12 "bookworm" (LTS): end of life

    Extension: Freexian ELTS until 30 Jun 2033

    Source: debian.org · Operating systems

    later
  5. Debian 13 "trixie": standard support ends

    Extension: Debian LTS until 30 Jun 2030

    Source: debian.org · Operating systems

    later
  6. TYPO3 v11 (ELTS): end of life

    ELTS is booked per year. The date is the latest possible end.

    Source: get.typo3.org · Frameworks & CMS

    later
  7. PostgreSQL 16: end of life

    Source: postgresql.org · Databases

    later
  8. PHP 8.4: security support ends

    Source: php.net · Runtimes

    later
End of support 2026 to 2028Live

How to read the calendar

Not every date means the same thing. Vendors end support in stages, so the calendar distinguishes four kinds of entry:

  • After standard support ends, security updates often continue in an extended phase, sometimes free, sometimes only for a fee. Ubuntu 22.04 LTS, for example, leaves standard support in May 2027, and Ubuntu Pro ESM provides updates until May 2032.
  • When full support ends, no new features or support for new hardware are added. Security updates continue, so this is not an EOL. RHEL 9, AlmaLinux 9 and Rocky Linux 9, for example, leave full support on 31 May 2027 and get security updates until 31 May 2032.
  • Once security support ends, the vendor no longer fixes security holes. For PHP 8.2 that date is 31 Dec 2026.
  • EOL means the product gets no updates at all from the vendor. For Node.js 22 that is the case from 30 Apr 2027.

Where a vendor names only a month, we show only the month, for example May 2027. Every entry has a status: ended, within the next six months, or later. We compute the status each time the page is rebuilt, which is once a week. We check the dates every week against the vendors’ pages, and the date of the last check is shown with the list.

Many products offer a paid extension after end of support:

  • from the vendor, for example Ubuntu Pro ESM, MariaDB Enterprise or TYPO3 ELTS,
  • or from long term support providers for runtimes and distributions, for example Zend PHP LTS, TuxCare or Freexian ELTS for Debian.

It often costs nothing extra if PHP comes from the packages of a supported distribution. The distribution then keeps shipping security fixes as backports for as long as it is supported itself.

Scope and price vary by provider, and some offers you book per year. An extension buys you time, but you still have to plan the upgrade.

When an entry affects you

  1. Find out where the version runs: on which servers, in which applications, containers and build jobs.
  2. Check which kind of end it is: standard support, full support, security support or EOL.
  3. Decide between an upgrade to a supported version, a paid extension and replacing the affected part.
  4. Plan the change, with a way back, for a maintenance window.

If you do not know which versions you run, it is best to start with the Legacy Check. In the check, we compare your inventory with this calendar, and you get an action plan. We plan upgrades and migrations as modernisation. As part of ongoing care and operations, we watch the calendar for you.

Patching is a loop, not a projectLifecycle and patch management with ITIL® practicesPatching is a loop, not a projectLifecycle and patch management with ITIL® practices1 InventoryWhat runs where, which versionService configuration mgmt.2 WatchEOL calendar, CVE advisoriesIT asset management3 AssessRisk and urgencyInformation security mgmt.4 PlanChange, maintenance windowChange enablement5 Roll out & verifyDeployment, functional testDeployment management6 ProveReport, NISG § 32Service level managementFixed cadenceevery round ends with evidencecritical: out of cycle

Move the mouse over a step or tap it. The step before and the one after stay highlighted.

An end of support date from this calendar becomes a planned change for us, with a risk assessment and a way back.
An end of support date from this calendar becomes a planned change for us, with a risk assessment and a way back.