Harbor 2.3 · Version Status
Harbor 2.3 End of Life Date
Harbor 2.3 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Harbor 2.3 is past end of life. This version no longer receives security patches. 1449 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 28, 2022
1449 days past EOL
Latest Release
2.3.5
Standard release
Release Date
Jun 17, 2021
Harbor 2.3 series
Lifecycle detail
Harbor 2.3 was released on June 17, 2021 and support ended on August 28, 2022 — a supported lifespan of 1 year and 2 months, in line with the 1 year and 2 months median for Harbor releases. The last patch it will ever receive is 2.3.5, published December 15, 2021 — 9 months before support ended. It has been without security patches for 4 years. 9 newer Harbor releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Harbor 2.3 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.9 |
1.9.4 |
Sep 18, 2020 |
EOL |
| 1.10 |
1.10.19 |
Feb 23, 2021 |
EOL |
| 2.0 |
2.0.6 |
Jun 17, 2021 |
EOL |
| 2.1 |
2.1.6 |
Oct 25, 2021 |
EOL |
| 2.2 |
2.2.4 |
Apr 7, 2022 |
EOL |
| → 2.3 |
2.3.5 |
Aug 28, 2022 |
EOL |
| 2.4 |
2.4.3 |
Dec 16, 2022 |
EOL |
| 2.5 |
2.5.6 |
Apr 13, 2023 |
EOL |
What does Harbor 2.3 end of life mean?
When Harbor 2.3 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Harbor 2.3 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Harbor 2.15 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Harbor 2.3 reach end of life?
Harbor 2.3 reached end of life on August 28, 2022. This version is no longer receiving security patches.
Is Harbor 2.3 still supported?
No. Harbor 2.3 reached end of life on August 28, 2022 and is no longer receiving security patches.
What should I upgrade to from Harbor 2.3?
The recommended upgrade from Harbor 2.3 is
Harbor 2.15 — the latest actively supported version. Check the
Harbor full timeline for all supported versions.
What are the security risks of running Harbor 2.3 past EOL?
When Harbor 2.3 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Harbor should migrate immediately or implement compensating controls.