Harbor End of Life (EOL) Dates & Support Timeline
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 | 2104 days past EOL | EOL |
| 1.10 | 1.10.19 | Dec 12, 2019 | Feb 23, 2021 | 1946 days past EOL | EOL |
| 2.0 | 2.0.6 | May 13, 2020 | Jun 17, 2021 | 1832 days past EOL | EOL |
| 2.1 | 2.1.6 | Sep 18, 2020 | Oct 25, 2021 | 1702 days past EOL | EOL |
| 2.2 | 2.2.4 | Feb 23, 2021 | Apr 7, 2022 | 1538 days past EOL | EOL |
| 2.3 | 2.3.5 | Jun 17, 2021 | Aug 28, 2022 | 1395 days past EOL | EOL |
| 2.4 | 2.4.3 | Oct 25, 2021 | Dec 16, 2022 | 1285 days past EOL | EOL |
| 2.5 | 2.5.6 | Apr 7, 2022 | Apr 13, 2023 | 1167 days past EOL | EOL |
| 2.6 | 2.6.4 | Aug 28, 2022 | Aug 31, 2023 | 1027 days past EOL | EOL |
| 2.7 | 2.7.4 | Dec 16, 2022 | Dec 14, 2023 | 922 days past EOL | EOL |
| 2.8 | 2.8.6 | Apr 13, 2023 | Jun 4, 2024 | 749 days past EOL | EOL |
| 2.9 | 2.9.5 | Aug 31, 2023 | Nov 8, 2024 | 592 days past EOL | EOL |
| 2.10 | 2.10.3 | Dec 14, 2023 | Apr 9, 2025 | 440 days past EOL | EOL |
| 2.11 | 2.11.2 | Jun 4, 2024 | Sep 17, 2025 | 279 days past EOL | EOL |
| 2.12 | 2.12.4 | Nov 5, 2024 | Mar 20, 2026 | 95 days past EOL | EOL |
| 2.13 | 2.13.5 | Apr 9, 2025 | TBD | Supported | Active |
| 2.14 | 2.14.4 | Sep 17, 2025 | TBD | Supported | Active |
| 2.15 | 2.15.1 | Mar 20, 2026 | TBD | Supported | Active |
What does Harbor end of life mean for your organization?
When a version of Harbor 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Harbor versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →