Explainer
What is EOL (end of life) in software?
EOL (end of life) is the date after which a software vendor or open-source project stops releasing security patches, bug fixes and support for a version. The software keeps running, but every vulnerability found afterwards stays unfixed unless you upgrade or get patches from someone else.
Dates checked 14 November 2026 against each vendor's lifecycle page and endoflife.date. Updated 14 November 2026.
EOL vs end of support vs end of extended support vs LTS
End of life and end of support often fall on the same date, but many vendors split support into stages: a full-support window, then a security-only window, then end of life. The terms below are the ones you will meet, with a dated example for each.
| Term | What it means | Who uses it | Example and source |
|---|---|---|---|
| End of life (EOL) | The date a project or vendor stops releasing security fixes for a version. After it, nothing is patched. | Open-source projects, most software vendors | Node.js 20 reached EOL on 30 April 2026; 20.20.2 was its last release (nodejs/Release via endoflife.date, checked 14 Nov 2026). |
| End of support (EOS) | The date the vendor stops supporting a version. Usually the same day as EOL, but it can also mark the end of help and bug fixes while security fixes continue. | Microsoft and other commercial vendors | .NET 8 and .NET 9 reached end of support on 10 November 2026 (endoflife.date, checked 14 Nov 2026). |
| Mainstream support, then extended support | Two stages. Mainstream support covers security and non-security updates; extended support continues security updates only, then the product reaches end of support. | Microsoft products under its Fixed Lifecycle Policy | Microsoft's policy gives at least five years of mainstream support, then extended support for some products (learn.microsoft.com/lifecycle/policies/fixed, checked 14 Nov 2026). |
| Open-source support vs commercial support | The project ends free security releases on one date and a commercial arm sells fixes for longer. | Spring | Spring Boot 3.4 open-source support ended 31 December 2025; spring.io lists commercial support until 31 December 2026 (spring.io/projects/spring-boot, checked 14 Nov 2026). |
| Long-term support (LTS) | A release line the project maintains for longer than its others. Its support still ends on a published date. | Node.js, Linux distributions, many projects | Node.js 22 is supported until 30 April 2027 (nodejs/Release via endoflife.date, checked 14 Nov 2026). |
| Fixed five-year window | Every major version gets the same support period, with no separate LTS label. | PostgreSQL | PostgreSQL 13 reached EOL on 13 November 2025 and 14 on 12 November 2026 (postgresql.org/support/versioning and endoflife.date, checked 14 Nov 2026). |
Vendor names and dates are as each vendor publishes them, checked 14 November 2026. Where two sources disagree, the vendor page wins.
What happens when software reaches end of life?
Nothing stops on the day itself. What stops is the flow of fixes, so CVEs published after that date accumulate on the version. The table counts CVEs that project and vendor CVE records published between 1 October and 14 November 2026 and whose affected range includes each line's final release. Spring Boot 2.7 shows 0 because no Spring project CVE was published in that window; the others took new CVEs in six weeks.
| Line | End of life | Final release | CVEs in window |
|---|---|---|---|
| Node.js 18 | 30 Apr 2025 | 18.20.8 | 10 |
| Node.js 20 | 30 Apr 2026 | 20.20.2 | 10 |
| Spring Boot 2.7 | 30 Jun 2023 | 2.7.18 | 0 |
| Tomcat 8.5 | 31 Mar 2024 | 8.5.100 | 2 |
| PostgreSQL 13 | 13 Nov 2025 | 13.23 | 40 |
Counted from vendor CVE records with NVD scores, pulled 14 November 2026. Node.js 18 and 20 share the same ten CVEs. Method, sources and every CVE are in the monthly EOL CVE round-up.
Is it safe, or allowed, to run EOL software?
It runs, but most security frameworks expect known vulnerabilities to be patched, and unsupported software makes that hard to show an auditor. Each framework below has its own guide.
- PCI DSS v4.0.1 Requirements 6.3.3 and 12.3.4: PCI DSS 6.3.3 and end-of-life software.
- FedRAMP and CMMC, through NIST SP 800-53 SI-2 and NIST SP 800-171 3.14.1: FedRAMP and CMMC end-of-life software.
- DORA and NIS2: DORA and NIS2 end-of-life software.
EOL dates in the next 90 days
Between mid-November 2026 and mid-February 2027, 7 open-source release lines tracked by OSSeva reach end of life or end of vendor support.
| Date | Product and line | What ends |
|---|---|---|
| 19 Nov 2026 | Hazelcast Platform 5.3 | Extended support ends; no patch releases |
| 1 Dec 2026 | Redis 8.0 | End of life (redis.io version management) |
| 31 Dec 2026 | Spring Boot 3.4 | Commercial support ends (open source ended 31 Dec 2025) |
| 31 Dec 2026 | Spring Boot 4.0 | Open-source support ends |
| 31 Dec 2026 | Spring Security 6.4 | Commercial support ends |
| 31 Dec 2026 | Spring Security 7.0 | Open-source support ends |
| 31 Jan 2027 | RabbitMQ 4.3 | Community support ends |
Dates checked 14 November 2026 on endoflife.date and each project's lifecycle page; each row links its own page. Every other date is in the EOL tracker and on the end-of-life dates by technology index.
How to find the EOL date for your software
Check the vendor's lifecycle page first, then a tracker such as endoflife.date or OSSeva's EOL tracker; the vendor page wins when they disagree.
- Find the exact version you run, including the minor release, not just the product name.
- Open the project or vendor lifecycle page and read the line for that version.
- Cross-check on the EOL tracker, for example Node.js EOL dates, Spring Boot EOL dates or Tomcat 9 end of life.
- Note whether the date is end of free support, end of commercial support or end of life, and write it down with the check date.
What to do when your version reaches end of life
You have four options: upgrade, buy extended support from the cloud or OS vendor, backport fixes yourself, or buy patched builds from a third party.
- Upgrade to a supported version, when the jump is small enough to finish before the date.
- Vendor extended support, such as a cloud provider's paid support for a managed service.
- Backport fixes yourself, which is practical for one component on one or two versions.
- Third-party patched builds, which keep an old version patched while you plan the move.
The detail, trade-offs and cost drivers are in end-of-life software options compared. Where OSSeva fits: it sells the fourth option, patched builds for the open-source versions on its supported versions list.
What does EOL stand for?
End of life.
Is EOL the same as end of support?
Often, but not always. For most open-source projects the two fall on the same day. Some vendors split support into stages, so end of support can come after a security-only window, and end of life marks the final date for any fix.
Does software stop working at end of life?
No. It keeps running and reports a valid version. What stops is the supply of security patches, so vulnerabilities published afterwards stay unfixed on that version.
What is LTS?
Long-term support. It is a release line the project maintains for longer than its others, usually with security fixes only in its later years. LTS lines still have an end-of-life date.
What is the difference between EOL and EOS?
EOL (end of life) is the date fixes stop. EOS (end of support) is the date the vendor stops supporting the version. They are often the same date; when they differ, check the vendor's lifecycle page for which fixes each stage includes.
Get a quote
Running a version that has reached end of life? Tell us which one.
Send your work email with the product and version. An engineer replies within 1 business day with an upgrade-or-cover recommendation.
Prefer to talk or read more first?