Harbor · Lifecycle Status

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.

Harbor 2.13.5 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
2.13.5
2.13 series
Next EOL
None upcoming
Active Versions
3
of 18 total
EOL Versions
15
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20202021202220232024202520261.91.102.02.12.22.32.42.52.62.72.82.92.102.112.122.132.142.15TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
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

What does Harbor end of life mean for your organization?

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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Harbor?
See the full table above for all Harbor version EOL dates.
What is the latest supported version of Harbor?
The latest active version of Harbor is 2.13.5. Always verify against the table above as support windows can change.
What happens when Harbor reaches end of life?
When Harbor reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Harbor?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Harbor versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →