Complete end-of-life dates, support windows, and security status for all Harbor versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.9 | 1.9.4 | Sep 17, 2019 | Sep 18, 2020 | 2059 days past EOL | EOL |
| 1.10 | 1.10.19 | Dec 12, 2019 | Feb 23, 2021 | 1901 days past EOL | EOL |
| 2.0 | 2.0.6 | May 13, 2020 | Jun 17, 2021 | 1787 days past EOL | EOL |
| 2.1 | 2.1.6 | Sep 18, 2020 | Oct 25, 2021 | 1657 days past EOL | EOL |
| 2.2 | 2.2.4 | Feb 23, 2021 | Apr 7, 2022 | 1493 days past EOL | EOL |
| 2.3 | 2.3.5 | Jun 17, 2021 | Aug 28, 2022 | 1350 days past EOL | EOL |
| 2.4 | 2.4.3 | Oct 25, 2021 | Dec 16, 2022 | 1240 days past EOL | EOL |
| 2.5 | 2.5.6 | Apr 7, 2022 | Apr 13, 2023 | 1122 days past EOL | EOL |
| 2.6 | 2.6.4 | Aug 28, 2022 | Aug 31, 2023 | 982 days past EOL | EOL |
| 2.7 | 2.7.4 | Dec 16, 2022 | Dec 14, 2023 | 877 days past EOL | EOL |
| 2.8 | 2.8.6 | Apr 13, 2023 | Jun 4, 2024 | 704 days past EOL | EOL |
| 2.9 | 2.9.5 | Aug 31, 2023 | Nov 8, 2024 | 547 days past EOL | EOL |
| 2.10 | 2.10.3 | Dec 14, 2023 | Apr 9, 2025 | 395 days past EOL | EOL |
| 2.11 | 2.11.2 | Jun 4, 2024 | Sep 17, 2025 | 234 days past EOL | EOL |
| 2.12 | 2.12.4 | Nov 5, 2024 | Mar 20, 2026 | 50 days past EOL | EOL |
| 2.13 | 2.13.5 | Apr 9, 2025 | Already EOL | Supported | Active |
| 2.14 | 2.14.3 | Sep 17, 2025 | Already EOL | Supported | Active |
| 2.15 | 2.15.1 | Mar 20, 2026 | Already EOL | Supported | Active |
When a Harbor 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 Harbor 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 →