Complete end-of-life dates, support windows, and security status for all Contour versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.24 | 1.24.6 | Jan 31, 2023 | Oct 30, 2023 | 922 days past EOL | EOL |
| 1.25 | 1.25.3 | May 9, 2023 | Feb 12, 2024 | 817 days past EOL | EOL |
| 1.26 | 1.26.3 | Aug 29, 2023 | May 7, 2024 | 732 days past EOL | EOL |
| 1.27 | 1.27.4 | Oct 30, 2023 | Jul 31, 2024 | 647 days past EOL | EOL |
| 1.28 | 1.28.8 | Feb 12, 2024 | May 6, 2025 | 368 days past EOL | EOL |
| 1.29 | 1.29.5 | May 7, 2024 | May 15, 2025 | 359 days past EOL | EOL |
| 1.30 | 1.30.5 | Jul 31, 2024 | Sep 8, 2025 | 243 days past EOL | EOL |
| 1.31 | 1.31.6 | May 6, 2025 | Already EOL | Supported | Active |
| 1.32 | 1.32.5 | May 15, 2025 | Already EOL | Supported | Active |
| 1.33 | 1.33.4 | Sep 8, 2025 | Already EOL | Supported | Active |
When a Contour 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 Contour 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 →