Complete end-of-life dates, support windows, and security status for all Cilium versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.13 | 1.13.18 | Feb 15, 2023 | Jul 24, 2024 | 654 days past EOL | EOL |
| 1.14 | 1.14.19 | Jul 27, 2023 | Feb 4, 2025 | 459 days past EOL | EOL |
| 1.15 | 1.15.19 | Jan 31, 2024 | Jul 29, 2025 | 284 days past EOL | EOL |
| 1.16 | 1.16.19 | Jul 24, 2024 | Feb 3, 2026 | 95 days past EOL | EOL |
| 1.17 | 1.17.15 | Feb 4, 2025 | Already EOL | Supported | Active |
| 1.18 | 1.18.9 | Jul 29, 2025 | Already EOL | Supported | Active |
| 1.19 | 1.19.3 | Feb 3, 2026 | Already EOL | Supported | Active |
When a Cilium 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 Cilium 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 →