← ← Back to all products
Cilium
Active
Server Software Latest Version: 1.19.0 Latest Release: Feb 3, 2026
Cilium is an eBPF-based networking, security, and observability solution for Kubernetes and cloud workloads.
Versions
7
Latest Version
1.19.0
Active Support
3
EOL
4
Lifecycle Timeline
Today ↓
1.19
1.19
1.18
1.18
1.17
1.17
1.16
1.16
1.15
1.15
1.14
1.14
1.13
1.13
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 1.19 | Feb 3, 2026 | - | No | 1.19.0 | No | Active |
| 1.18 | Jul 29, 2025 | - | No | 1.18.7 | No | Active |
| 1.17 | Feb 4, 2025 | - | No | 1.17.13 | No | Active |
| 1.16 | Jul 24, 2024 | - | Feb 3, 2026 | 1.16.19 | No | EOL |
| 1.15 | Jan 31, 2024 | - | Jul 29, 2025 | 1.15.19 | No | EOL |
| 1.14 | Jul 27, 2023 | - | Feb 4, 2025 | 1.14.19 | No | EOL |
| 1.13 | Feb 15, 2023 | - | Jul 24, 2024 | 1.13.18 | No | EOL |
Frequently Asked Questions
Which versions of Cilium have reached end of life?
The following Cilium versions have reached end of life and no longer receive security updates: 1.16, 1.15, 1.14, 1.13. It is recommended to upgrade to a supported version.
Is it safe to continue using Cilium 1.16?
Cilium 1.16 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Cilium?
The latest version of Cilium is 1.19.0, released in the 1.19 release cycle.
How many versions of Cilium are currently supported?
Cilium currently has 3 actively supported version(s): 1.19, 1.18, 1.17.
When does Cilium 1.19 reach end of life?
Cilium 1.19 does not have a specific end-of-life date announced yet.
What should I do when Cilium reaches end of life?
When a Cilium version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.