Cilium versions
Cilium: update to 1.20.5, 1.19.11 or 1.18.17. 1.17 and older no longer get fixes.
Data: .
Which Cilium branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 1.20 | Fixes, no end date announced | 1.20.5 | 1.20.5 (this branch) |
| 1.196 CVE records that this page reads | Fixes, no end date announced | 1.19.11 | 1.19.11 (this branch) |
| 1.187 CVE records that this page reads | Fixes, no end date announced | 1.18.17 | 1.18.17 (this branch) |
| 1.179 CVE records that this page reads | Ended on 29 July 2026 | None, the branch has ended | 1.18.17 (move to 1.18) |
| 1.169 CVE records that this page reads | Ended on 3 February 2026 | None, the branch has ended | 1.18.17 (move to 1.18) |
| 1.1513 CVE records that this page reads | Ended on 29 July 2025 | None, the branch has ended | 1.18.17 (move to 1.18) |
| 1.1411 CVE records that this page reads | Ended on 4 February 2025 | None, the branch has ended | 1.18.17 (move to 1.18) |
| 1.136 CVE records that this page reads | Ended on 24 July 2024 | None, the branch has ended | 1.18.17 (move to 1.18) |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
This page reads 36 CVE records that the CVE Numbering Authority GitHub_M (as the CVE List names it) published and that name Cilium. The fixes are from the 27 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
No release of a branch that has ended is called safe here.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.
9 records are not placed on a branch, so no branch or release row counts them: CVE-2022-29178, CVE-2022-29179, CVE-2023-27593, CVE-2023-27594, CVE-2023-29002, CVE-2023-30851, CVE-2023-39347, CVE-2023-41332 and CVE-2023-41333.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)