Harbor End of Life Dates
other
Developers working with containerization and cloud-native technologies often require a reliable and secure way to manage their container images, which is where Harbor comes into play, providing a sheltered environment for containerized applications. Created to address the need for a trusted and scalable container registry, Harbor has been maintained by a community-driven effort, ensuring its stability and security. With its origins dating back to its initial release, Harbor has gained popularity among developers due to its ability to provide a robust and feature-rich platform for managing container images.
The end-of-life landscape for Harbor is characterized by a total of 18 versions, out of which 15 have reached their end-of-life, leaving only 3 active versions. The latest stable version, 2.15.1, is the current benchmark for users. Although there is no next end-of-life date announced, the last end-of-life date was marked on 2026-03-20, when version 2.12 ceased to receive support. This EOL milestone serves as a reminder for developers to ensure they are running the latest versions of Harbor to avoid potential security risks associated with outdated software.
From a security standpoint, Harbor boasts an impressive track record with a total of 0 CVEs tracked, and consequently, 0 critical CVEs. This flawless security record means that there is no most affected version, as no vulnerabilities have been discovered. With no known vulnerabilities, Harbor's KEV status is not applicable, and developers can continue to use the platform without immediate concern for security patches. However, it is still essential for developers to stay up-to-date with the latest versions of Harbor to ensure they benefit from the latest features and any future security enhancements, thereby maintaining the integrity and reliability of their containerized applications.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2.15 | Mar 20, 2026 | — | No | — | 2.15.2 | — | Active | |
| 2.14 | Sep 17, 2025 | — | No | — | 2.14.4 | — | Active | |
| 2.13 | Apr 9, 2025 | — | No | — | 2.13.5 | — | Active | |
| 2.12 | Nov 5, 2024 | — | Mar 20, 2026 | 126d ago | 2.12.4 | — | EOL | |
| 2.11 | Jun 4, 2024 | — | Sep 17, 2025 | 310d ago | 2.11.2 | — | EOL | |
| 2.10 | Dec 14, 2023 | — | Apr 9, 2025 | 471d ago | 2.10.3 | — | EOL | |
| 2.9 | Aug 31, 2023 | — | Nov 8, 2024 | 623d ago | 2.9.5 | — | EOL | |
| 2.8 | Apr 13, 2023 | — | Jun 4, 2024 | 780d ago | 2.8.6 | — | EOL | |
| 2.7 | Dec 16, 2022 | — | Dec 14, 2023 | 953d ago | 2.7.4 | — | EOL | |
| 2.6 | Aug 28, 2022 | — | Aug 31, 2023 | 1058d ago | 2.6.4 | — | EOL | |
| 2.5 | Apr 7, 2022 | — | Apr 13, 2023 | 1198d ago | 2.5.6 | — | EOL | |
| 2.4 | Oct 25, 2021 | — | Dec 16, 2022 | 1316d ago | 2.4.3 | — | EOL | |
| 2.3 | Jun 17, 2021 | — | Aug 28, 2022 | 1426d ago | 2.3.5 | — | EOL | |
| 2.2 | Feb 23, 2021 | — | Apr 7, 2022 | 1569d ago | 2.2.4 | — | EOL | |
| 2.1 | Sep 18, 2020 | — | Oct 25, 2021 | 1733d ago | 2.1.6 | — | EOL | |
| 2.0 | May 13, 2020 | — | Jun 17, 2021 | 1863d ago | 2.0.6 | — | EOL | |
| 1.10 | Dec 12, 2019 | — | Feb 23, 2021 | 1977d ago | 1.10.19 | — | EOL | |
| 1.9 | Sep 17, 2019 | — | Sep 18, 2020 | 2135d ago | 1.9.4 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
