Updated August 2, 2026: dates verified against vendor lifecycle data.
2026 is one of the most significant years for software end-of-life in recent memory. Multiple major LTS releases, widely-deployed operating systems, and enterprise-grade frameworks are all reaching the end of their support windows this year.
This is your complete reference — every major EOL event in 2026, organized by month.
Why 2026 Is a Critical Year
The 2021–2022 wave of LTS releases — Ubuntu 20.04, MariaDB 10.6, Django 4.2 — are all hitting their 5-year windows in 2025–2026. Organizations that chose LTS versions for stability are now facing simultaneous migration pressure across their entire stack.
The EOL Risk Score™ for any component scoring 76+ (Critical) means immediate action is warranted. Check any version at endoflife.ai.
Q1 2026 — January to March
Kubernetes 1.31 reached EOL ahead of schedule — on November 11, 2025 (final patch 1.31.14), not the originally planned January 2026 date. If you're still on 1.31, upgrade to K8s 1.35 or 1.36 now.
February 28, 2026
- Kubernetes 1.32 — EOL. Skip 1.33 (EOL June 2026) and go straight to 1.35+.
Q2 2026 — April to June
April 1, 2026
- Ruby 3.2 — EOL. Upgrade to Ruby 3.3 or 3.4.
April 7, 2026
- Django 4.2 LTS — EOL. The most widely deployed Django LTS version. Upgrade to Django 5.2 LTS. EOL Risk Score™: 76 Critical.
April 30, 2026
- Node.js 20 — EOL. Upgrade to Node.js 22 LTS. EOL Risk Score™: 72 Critical.
June 28, 2026
- Kubernetes 1.33 — EOL. Upgrade to K8s 1.35 or 1.36.
Q3 2026 — July to September
July 6, 2026
- MariaDB 10.6 LTS — EOL. Upgrade to MariaDB 10.11 or 11.4 LTS.
July 11, 2026
- Debian 12 (Bookworm) — Regular support ended (the date slipped from the originally announced June 10). Now on LTS until June 30, 2028; package coverage narrows.
August 31, 2026
- Debian 11 (Bullseye) — LTS ends. All community patches stop. Only ELTS (paid) remains.
Correction: PHP 8.1 security support ended December 31, 2025 — earlier than this calendar originally estimated. If you're still on PHP 8.1, upgrade to PHP 8.4 or 8.5 now.
Q4 2026 — October to December
October 27, 2026
- Kubernetes 1.34 — EOL. Stay current with K8s 1.36+.
October 31, 2026
- Python 3.10 — EOL. Upgrade to Python 3.12 or 3.13. EOL Risk Score™: High.
December 2026
- PHP 8.2 — Security support ends. Upgrade to PHP 8.3 or 8.4.
Already EOL — Action Required Now
These reached EOL before 2026 but are still widely running in production:
| Product | EOL Date | EOL Risk Score™ | Action |
|---|---|---|---|
| PHP 7.4 | Nov 2022 | 90 Critical | Upgrade to PHP 8.3+ immediately |
| Python 3.8 | Oct 2024 | 88 Critical | Upgrade to Python 3.12+ |
| Node.js 18 | Apr 2025 | 85 Critical | Upgrade to Node.js 22 LTS |
| Spring 5.3 | Dec 2024 | 82 Critical | Upgrade to Spring 6.x |
| Ubuntu 20.04 | May 2025 | 80 Critical | Upgrade to Ubuntu 24.04 LTS |
| RHEL 7 | Jun 2024 | 88 Critical | Upgrade to RHEL 9 or 10 |
| Debian 10 | Jun 2024 | 86 Critical | Upgrade to Debian 13 |
| Node.js 16 | Sep 2023 | 91 Critical | Upgrade to Node.js 22 LTS |
| Ruby 3.1 | Mar 2025 | — | Upgrade to Ruby 3.3 or 3.4 |
How to Stay Ahead of EOL Events
Use the endoflife.ai API to query upcoming EOL dates programmatically and build automated alerts into your CI/CD pipeline or ITSM system.
Set 90-day and 180-day lead time reminders for every EOL date in this calendar. 90 days is the minimum time to plan and execute most migrations. 180 days is realistic for complex environments.
Document everything. For compliance frameworks (SOC 2, PCI DSS, HIPAA), an EOL date in your inventory without a migration plan is a finding. An EOL date with a documented plan and compensating controls is a managed risk.
Track all of these at endoflife.ai — free EOL checker, stack scanner, and EOL Risk Score™ for 455+ products. No signup required.
Top comments (0)