Slackware End of Life Dates

other

Developers rely on accurate and up-to-date information to manage their systems effectively, and when it comes to tracking end-of-life dates for Linux distributions, having the right data is crucial. Slackware, a long-standing Linux distribution created in 1993 by Patrick Volkerding, is one such system that requires careful planning for upgrades and maintenance. With the Slackware team maintaining the distribution, developers use this information to plan their upgrades and ensure their systems remain secure and supported. The Slackware project provides a stable and reliable platform for developers to build and deploy their applications, and by tracking its end-of-life dates, they can avoid potential security risks and compatibility issues.

The end-of-life landscape for Slackware is characterized by a large number of versions that have reached their end of support, with 17 out of 18 versions no longer receiving updates or security patches. The latest stable version, 15.0, is the only active version currently supported, and with no next EOL date announced, developers can focus on upgrading to this version to ensure they receive the latest security patches and updates. The last EOL date was on 2024-01-01, when version 14.0 reached the end of its support cycle, marking an important milestone in the distribution's lifecycle. By tracking these dates, developers can plan their upgrades and migrations to newer versions, minimizing downtime and ensuring continuity of their operations.

From a security perspective, Slackware has a clean track record, with no known CVEs or critical vulnerabilities reported. This is a significant advantage for developers who rely on the distribution for their critical systems and applications. With no critical CVEs to worry about, developers can focus on other aspects of their system's security, such as configuration and access control. As the distribution is not listed on the Known Exploited Vulnerabilities catalog, developers can be confident that their systems are not exposed to known vulnerabilities. To maintain this level of security, developers should continue to track the end-of-life dates for Slackware and plan their upgrades accordingly, ensuring their systems remain up-to-date and secure.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
15.0 Feb 3, 2022—No—15.0—Active
14.2 Jul 1, 2016—Jan 1, 20241026d ago14.2—EOL
14.1 Nov 7, 2013—Jan 1, 20241026d ago14.1—EOL
14.0 Sep 28, 2012—Jan 1, 20241026d ago14.0—EOL
13.37 Apr 28, 2011—Jul 5, 20183032d ago13.37—EOL
13.1 May 24, 2010—Jul 5, 20183032d ago13.1—EOL
13.0 Aug 28, 2009—Jul 5, 20183032d ago13.0—EOL
12.2 Dec 11, 2008—Dec 9, 20134701d ago12.2—EOL
12.1 May 2, 2008—Dec 9, 20134701d ago12.1—EOL
12.0 Jul 2, 2007—Aug 1, 20125196d ago12.0—EOL
11.0 Oct 3, 2006—Aug 1, 20125196d ago11.0—EOL
10.2 Sep 15, 2005—Aug 1, 20125196d ago10.2—EOL
10.1 Feb 7, 2005—Aug 1, 20125196d ago10.1—EOL
10.0 Jun 23, 2004—Aug 1, 20125196d ago10.0—EOL
9.1 Sep 26, 2003—Aug 1, 20125196d ago9.1—EOL
9.0 Mar 18, 2003—Aug 1, 20125196d ago——EOL
8.1 Jun 19, 2002—Aug 1, 20125196d ago8.1—EOL
8.0 Jul 1, 2001—Mar 29, 20038609d ago8.0—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions