Complete end-of-life dates, support windows, and security status for all Tails versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.8.2 | Apr 29, 2014 | Jan 25, 2016 | 3757 days past EOL | EOL |
| 2 | 2.12 | Jan 27, 2016 | Jul 10, 2017 | 3225 days past EOL | EOL |
| 3 | 3.16 | Jun 13, 2017 | Oct 21, 2019 | 2392 days past EOL | EOL |
| 4 | 4.29 | Oct 22, 2019 | May 2, 2022 | 1468 days past EOL | EOL |
| 5 | 5.22 | May 3, 2022 | Feb 27, 2024 | 802 days past EOL | EOL |
| 6 | 6.19 | Feb 27, 2024 | Sep 18, 2025 | 233 days past EOL | EOL |
| 7 | 7.7.2 | Sep 18, 2025 | Already EOL | Supported | Active |
When a Tails 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 Tails 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 →