GitLab End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all GitLab versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 13.10 | 13.10.5 | Mar 18, 2021 | Jun 22, 2021 | 1874 days past EOL | EOL |
| 13.11 | 13.11.7 | Apr 21, 2021 | Jul 22, 2021 | 1844 days past EOL | EOL |
| 13.12 | 13.12.15 | May 21, 2021 | Aug 22, 2021 | 1813 days past EOL | EOL |
| 14.0 | 14.0.12 | Jun 21, 2021 | Sep 22, 2021 | 1782 days past EOL | EOL |
| 14.1 | 14.1.8 | Jul 21, 2021 | Oct 22, 2021 | 1752 days past EOL | EOL |
| 14.2 | 14.2.7 | Aug 20, 2021 | Nov 22, 2021 | 1721 days past EOL | EOL |
| 14.3 | 14.3.6 | Sep 21, 2021 | Dec 22, 2021 | 1691 days past EOL | EOL |
| 14.4 | 14.4.5 | Oct 21, 2021 | Jan 22, 2022 | 1660 days past EOL | EOL |
| 14.5 | 14.5.4 | Nov 19, 2021 | Feb 22, 2022 | 1629 days past EOL | EOL |
| 14.6 | 14.6.7 | Dec 21, 2021 | Mar 22, 2022 | 1601 days past EOL | EOL |
| 14.7 | 14.7.7 | Jan 21, 2022 | Apr 22, 2022 | 1570 days past EOL | EOL |
| 14.8 | 14.8.6 | Feb 21, 2022 | May 22, 2022 | 1540 days past EOL | EOL |
| 14.9 | 14.9.5 | Mar 21, 2022 | Jun 22, 2022 | 1509 days past EOL | EOL |
| 14.10 | 14.10.5 | Apr 21, 2022 | Jul 22, 2022 | 1479 days past EOL | EOL |
| 15.0 | 15.0.5 | May 20, 2022 | Aug 22, 2022 | 1448 days past EOL | EOL |
| 15.1 | 15.1.6 | Jun 21, 2022 | Sep 22, 2022 | 1417 days past EOL | EOL |
| 15.2 | 15.2.5 | Jul 21, 2022 | Oct 22, 2022 | 1387 days past EOL | EOL |
| 15.3 | 15.3.5 | Aug 19, 2022 | Nov 22, 2022 | 1356 days past EOL | EOL |
| 15.4 | 15.4.6 | Sep 21, 2022 | Dec 22, 2022 | 1326 days past EOL | EOL |
| 15.5 | 15.5.9 | Oct 21, 2022 | Jan 22, 2023 | 1295 days past EOL | EOL |
| 15.6 | 15.6.8 | Nov 21, 2022 | Feb 22, 2023 | 1264 days past EOL | EOL |
| 15.7 | 15.7.9 | Dec 21, 2022 | Mar 22, 2023 | 1236 days past EOL | EOL |
| 15.8 | 15.8.6 | Jan 20, 2023 | Apr 22, 2023 | 1205 days past EOL | EOL |
| 15.9 | 15.9.8 | Feb 21, 2023 | May 22, 2023 | 1175 days past EOL | EOL |
| 15.10 | 15.10.8 | Mar 21, 2023 | Jun 22, 2023 | 1144 days past EOL | EOL |
| 15.11 | 15.11.13 | Apr 21, 2023 | Jul 22, 2023 | 1114 days past EOL | EOL |
| 16.0 | 16.0.10 | May 18, 2023 | Aug 22, 2023 | 1083 days past EOL | EOL |
| 16.1 | 16.1.8 | Jun 21, 2023 | Sep 22, 2023 | 1052 days past EOL | EOL |
| 16.2 | 16.2.11 | Jul 21, 2023 | Oct 22, 2023 | 1022 days past EOL | EOL |
| 16.3 | 16.3.9 | Aug 21, 2023 | Nov 16, 2023 | 997 days past EOL | EOL |
| 16.4 | 16.4.7 | Sep 21, 2023 | Dec 21, 2023 | 962 days past EOL | EOL |
| 16.5 | 16.5.10 | Oct 20, 2023 | Jan 18, 2024 | 934 days past EOL | EOL |
| 16.6 | 16.6.10 | Nov 15, 2023 | Feb 15, 2024 | 906 days past EOL | EOL |
| 16.7 | 16.7.10 | Dec 20, 2023 | Mar 21, 2024 | 871 days past EOL | EOL |
| 16.8 | 16.8.10 | Jan 17, 2024 | Apr 18, 2024 | 843 days past EOL | EOL |
| 16.9 | 16.9.11 | Feb 14, 2024 | May 16, 2024 | 815 days past EOL | EOL |
| 16.10 | 16.10.10 | Mar 20, 2024 | Jun 20, 2024 | 780 days past EOL | EOL |
| 16.11 | 16.11.10 | Apr 17, 2024 | Jul 18, 2024 | 752 days past EOL | EOL |
| 17.0 | 17.0.8 | May 15, 2024 | Aug 15, 2024 | 724 days past EOL | EOL |
| 17.1 | 17.1.8 | Jun 19, 2024 | Sep 19, 2024 | 689 days past EOL | EOL |
| 17.2 | 17.2.9 | Jul 17, 2024 | Oct 17, 2024 | 661 days past EOL | EOL |
| 17.3 | 17.3.7 | Aug 14, 2024 | Nov 21, 2024 | 626 days past EOL | EOL |
| 17.4 | 17.4.6 | Sep 18, 2024 | Dec 19, 2024 | 598 days past EOL | EOL |
| 17.5 | 17.5.5 | Oct 16, 2024 | Jan 16, 2025 | 570 days past EOL | EOL |
| 17.6 | 17.6.5 | Nov 20, 2024 | Feb 20, 2025 | 535 days past EOL | EOL |
| 17.7 | 17.7.7 | Dec 18, 2024 | Mar 20, 2025 | 507 days past EOL | EOL |
| 17.8 | 17.8.7 | Jan 15, 2025 | Apr 17, 2025 | 479 days past EOL | EOL |
| 17.9 | 17.9.8 | Feb 19, 2025 | May 15, 2025 | 451 days past EOL | EOL |
| 17.10 | 17.10.8 | Mar 19, 2025 | Jun 19, 2025 | 416 days past EOL | EOL |
| 17.11 | 17.11.7 | Apr 16, 2025 | Jul 17, 2025 | 388 days past EOL | EOL |
| 18.0 | 18.0.6 | May 14, 2025 | Aug 21, 2025 | 353 days past EOL | EOL |
| 18.1 | 18.1.6 | Jun 18, 2025 | Sep 18, 2025 | 325 days past EOL | EOL |
| 18.2 | 18.2.8 | Jul 16, 2025 | Oct 16, 2025 | 297 days past EOL | EOL |
| 18.3 | 18.3.6 | Aug 21, 2025 | Nov 20, 2025 | 262 days past EOL | EOL |
| 18.4 | 18.4.6 | Sep 18, 2025 | Dec 18, 2025 | 234 days past EOL | EOL |
| 18.5 | 18.5.7 | Oct 16, 2025 | Jan 15, 2026 | 206 days past EOL | EOL |
| 18.6 | 18.6.8 | Nov 20, 2025 | Feb 19, 2026 | 171 days past EOL | EOL |
| 18.7 | 18.7.7 | Dec 18, 2025 | Mar 19, 2026 | 143 days past EOL | EOL |
| 18.8 | 18.8.11 | Jan 15, 2026 | Apr 16, 2026 | 115 days past EOL | EOL |
| 18.9 | 18.9.8 | Feb 19, 2026 | May 21, 2026 | 80 days past EOL | EOL |
| 18.10 | 18.10.8 | Mar 19, 2026 | Jun 18, 2026 | 52 days past EOL | EOL |
| 18.11 | 18.11.9 | Apr 16, 2026 | Jul 16, 2026 | 24 days past EOL | EOL |
| 19.0 | 19.0.5 | May 21, 2026 | Aug 20, 2026 | 11 days remaining | Warning |
| 19.1 | 19.1.3 | Jun 18, 2026 | Sep 17, 2026 | 39 days remaining | Warning |
| 19.2 | 19.2.1 | Jul 16, 2026 | Oct 15, 2026 | 67 days remaining | Warning |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/gitlab)
What does GitLab end of life mean for your organization?
When a version of GitLab 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 GitLab 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.
Your options when GitLab reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL GitLab versions. This is a bridge, not a permanent solution — plan your migration in parallel.
GitLab has 62 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for GitLab exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.