Complete end-of-life dates, support windows, and security status for all Cos versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| cos-69 LTS | cos-69-10895-385-0 | Sep 18, 2018 | Dec 1, 2019 | 2351 days past EOL | EOL |
| cos-73 LTS | cos-73-11647-656-0 | Mar 25, 2019 | Jun 1, 2020 | 2168 days past EOL | EOL |
| cos-77 LTS | cos-77-12371-1109-0 | Sep 27, 2019 | Apr 1, 2021 | 1864 days past EOL | EOL |
| cos-81 LTS | cos-81-12871-1317-8 | Mar 27, 2020 | Sep 1, 2021 | 1711 days past EOL | EOL |
| cos-85 LTS | cos-85-13310-1498-13 | Sep 24, 2020 | Sep 1, 2022 | 1346 days past EOL | EOL |
| cos-89 LTS | cos-89-16108-798-22 | Apr 7, 2021 | Mar 1, 2023 | 1165 days past EOL | EOL |
| cos-93 LTS | cos-93-16623-461-42 | Oct 18, 2021 | Oct 1, 2023 | 951 days past EOL | EOL |
| cos-97 LTS | cos-97-16919-450-41 | Mar 29, 2022 | Mar 1, 2024 | 799 days past EOL | EOL |
| cos-101 LTS | cos-101-17162-528-64 | Sep 15, 2022 | Sep 1, 2024 | 615 days past EOL | EOL |
| cos-105 LTS | cos-105-17412-535-98 | Apr 3, 2023 | Apr 1, 2025 | 403 days past EOL | EOL |
| cos-109 LTS | cos-109-17800-570-50 | Sep 27, 2023 | Sep 1, 2025 | 250 days past EOL | EOL |
| cos-113 LTS | cos-113-18244-582-100 | Apr 15, 2024 | Mar 1, 2026 | 69 days past EOL | EOL |
| cos-117 LTS | cos-117-18613-534-110 | Oct 2, 2024 | Sep 1, 2026 | 115 days remaining | Warning |
| cos-121 LTS | cos-121-18867-381-118 | Apr 14, 2025 | Mar 1, 2027 | 296 days remaining | Active |
| cos-125 LTS | cos-125-19216-220-185 | Oct 9, 2025 | Sep 1, 2027 | 480 days remaining | Active |
When a Cos 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 Cos 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 →