Complete end-of-life dates, support windows, and security status for all Slackware versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 8.0 | 8.0 | Jul 1, 2001 | Mar 29, 2003 | 8442 days past EOL | EOL |
| 8.1 | 8.1 | Jun 19, 2002 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 9.0 | — | Mar 18, 2003 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 9.1 | 9.1 | Sep 26, 2003 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 10.0 | 10.0 | Jun 23, 2004 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 10.1 | 10.1 | Feb 7, 2005 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 10.2 | 10.2 | Sep 15, 2005 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 11.0 | 11.0 | Oct 3, 2006 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 12.0 | 12.0 | Jul 2, 2007 | Aug 1, 2012 | 5029 days past EOL | EOL |
| 12.1 | 12.1 | May 2, 2008 | Dec 9, 2013 | 4534 days past EOL | EOL |
| 12.2 | 12.2 | Dec 11, 2008 | Dec 9, 2013 | 4534 days past EOL | EOL |
| 13.0 | 13.0 | Aug 28, 2009 | Jul 5, 2018 | 2865 days past EOL | EOL |
| 13.1 | 13.1 | May 24, 2010 | Jul 5, 2018 | 2865 days past EOL | EOL |
| 13.37 | 13.37 | Apr 28, 2011 | Jul 5, 2018 | 2865 days past EOL | EOL |
| 14.0 | 14.0 | Sep 28, 2012 | Jan 1, 2024 | 859 days past EOL | EOL |
| 14.1 | 14.1 | Nov 7, 2013 | Jan 1, 2024 | 859 days past EOL | EOL |
| 14.2 | 14.2 | Jul 1, 2016 | Jan 1, 2024 | 859 days past EOL | EOL |
| 15.0 | 15.0 | Feb 3, 2022 | Already EOL | Supported | Active |
When a Slackware version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Slackware should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →