Complete end-of-life dates, support windows, and security status for all Calico versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.25 | 3.25.2 | Jan 11, 2023 | Dec 15, 2023 | 876 days past EOL | EOL |
| 3.26 | 3.26.5 | May 27, 2023 | May 11, 2024 | 728 days past EOL | EOL |
| 3.27 | 3.27.5 | Dec 15, 2023 | Oct 29, 2024 | 557 days past EOL | EOL |
| 3.28 | 3.28.5 | May 10, 2024 | May 5, 2025 | 369 days past EOL | EOL |
| 3.29 | 3.29.7 | Oct 29, 2024 | Oct 21, 2025 | 200 days past EOL | EOL |
| 3.30 | 3.30.7 | May 5, 2025 | Already EOL | Supported | Active |
| 3.31 | 3.31.5 | Oct 21, 2025 | Already EOL | Supported | Active |
When a Calico 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 Calico 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 →