GitLab · Lifecycle Status

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.

GitLab 18.11 reaches end of life on July 16, 2026. Plan your migration now — 3 days remaining.
📅 Get reminded before GitLab 18.11 reaches EOL on July 16, 2026 — alerts 90, 30 & 7 days out.
Google →
Latest Active
— series
Next EOL
18.11
Jul 16, 2026
Active Versions
0
of 64 total
EOL Versions
61
no longer patched
65 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Yes — CISA 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 →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2022202320242025202613.1013.1113.1214.014.114.214.314.414.514.614.714.814.914.1015.015.115.215.315.415.515.615.715.815.915.1015.1116.016.116.216.316.416.516.616.716.816.916.1016.1117.017.117.217.317.417.517.617.717.817.917.1017.1118.018.118.218.318.418.518.618.718.818.918.1018.1119.019.1TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
13.10 13.10.5 Mar 18, 2021 Jun 22, 2021 1847 days past EOL EOL
13.11 13.11.7 Apr 21, 2021 Jul 22, 2021 1817 days past EOL EOL
13.12 13.12.15 May 21, 2021 Aug 22, 2021 1786 days past EOL EOL
14.0 14.0.12 Jun 21, 2021 Sep 22, 2021 1755 days past EOL EOL
14.1 14.1.8 Jul 21, 2021 Oct 22, 2021 1725 days past EOL EOL
14.2 14.2.7 Aug 20, 2021 Nov 22, 2021 1694 days past EOL EOL
14.3 14.3.6 Sep 21, 2021 Dec 22, 2021 1664 days past EOL EOL
14.4 14.4.5 Oct 21, 2021 Jan 22, 2022 1633 days past EOL EOL
14.5 14.5.4 Nov 19, 2021 Feb 22, 2022 1602 days past EOL EOL
14.6 14.6.7 Dec 21, 2021 Mar 22, 2022 1574 days past EOL EOL
14.7 14.7.7 Jan 21, 2022 Apr 22, 2022 1543 days past EOL EOL
14.8 14.8.6 Feb 21, 2022 May 22, 2022 1513 days past EOL EOL
14.9 14.9.5 Mar 21, 2022 Jun 22, 2022 1482 days past EOL EOL
14.10 14.10.5 Apr 21, 2022 Jul 22, 2022 1452 days past EOL EOL
15.0 15.0.5 May 20, 2022 Aug 22, 2022 1421 days past EOL EOL
15.1 15.1.6 Jun 21, 2022 Sep 22, 2022 1390 days past EOL EOL
15.2 15.2.5 Jul 21, 2022 Oct 22, 2022 1360 days past EOL EOL
15.3 15.3.5 Aug 19, 2022 Nov 22, 2022 1329 days past EOL EOL
15.4 15.4.6 Sep 21, 2022 Dec 22, 2022 1299 days past EOL EOL
15.5 15.5.9 Oct 21, 2022 Jan 22, 2023 1268 days past EOL EOL
15.6 15.6.8 Nov 21, 2022 Feb 22, 2023 1237 days past EOL EOL
15.7 15.7.9 Dec 21, 2022 Mar 22, 2023 1209 days past EOL EOL
15.8 15.8.6 Jan 20, 2023 Apr 22, 2023 1178 days past EOL EOL
15.9 15.9.8 Feb 21, 2023 May 22, 2023 1148 days past EOL EOL
15.10 15.10.8 Mar 21, 2023 Jun 22, 2023 1117 days past EOL EOL
15.11 15.11.13 Apr 21, 2023 Jul 22, 2023 1087 days past EOL EOL
16.0 16.0.10 May 18, 2023 Aug 22, 2023 1056 days past EOL EOL
16.1 16.1.8 Jun 21, 2023 Sep 22, 2023 1025 days past EOL EOL
16.2 16.2.11 Jul 21, 2023 Oct 22, 2023 995 days past EOL EOL
16.3 16.3.9 Aug 21, 2023 Nov 16, 2023 970 days past EOL EOL
16.4 16.4.7 Sep 21, 2023 Dec 21, 2023 935 days past EOL EOL
16.5 16.5.10 Oct 20, 2023 Jan 18, 2024 907 days past EOL EOL
16.6 16.6.10 Nov 15, 2023 Feb 15, 2024 879 days past EOL EOL
16.7 16.7.10 Dec 20, 2023 Mar 21, 2024 844 days past EOL EOL
16.8 16.8.10 Jan 17, 2024 Apr 18, 2024 816 days past EOL EOL
16.9 16.9.11 Feb 14, 2024 May 16, 2024 788 days past EOL EOL
16.10 16.10.10 Mar 20, 2024 Jun 20, 2024 753 days past EOL EOL
16.11 16.11.10 Apr 17, 2024 Jul 18, 2024 725 days past EOL EOL
17.0 17.0.8 May 15, 2024 Aug 15, 2024 697 days past EOL EOL
17.1 17.1.8 Jun 19, 2024 Sep 19, 2024 662 days past EOL EOL
17.2 17.2.9 Jul 17, 2024 Oct 17, 2024 634 days past EOL EOL
17.3 17.3.7 Aug 14, 2024 Nov 21, 2024 599 days past EOL EOL
17.4 17.4.6 Sep 18, 2024 Dec 19, 2024 571 days past EOL EOL
17.5 17.5.5 Oct 16, 2024 Jan 16, 2025 543 days past EOL EOL
17.6 17.6.5 Nov 20, 2024 Feb 20, 2025 508 days past EOL EOL
17.7 17.7.7 Dec 18, 2024 Mar 20, 2025 480 days past EOL EOL
17.8 17.8.7 Jan 15, 2025 Apr 17, 2025 452 days past EOL EOL
17.9 17.9.8 Feb 19, 2025 May 15, 2025 424 days past EOL EOL
17.10 17.10.8 Mar 19, 2025 Jun 19, 2025 389 days past EOL EOL
17.11 17.11.7 Apr 16, 2025 Jul 17, 2025 361 days past EOL EOL
18.0 18.0.6 May 14, 2025 Aug 21, 2025 326 days past EOL EOL
18.1 18.1.6 Jun 18, 2025 Sep 18, 2025 298 days past EOL EOL
18.2 18.2.8 Jul 16, 2025 Oct 16, 2025 270 days past EOL EOL
18.3 18.3.6 Aug 21, 2025 Nov 20, 2025 235 days past EOL EOL
18.4 18.4.6 Sep 18, 2025 Dec 18, 2025 207 days past EOL EOL
18.5 18.5.7 Oct 16, 2025 Jan 15, 2026 179 days past EOL EOL
18.6 18.6.8 Nov 20, 2025 Feb 19, 2026 144 days past EOL EOL
18.7 18.7.7 Dec 18, 2025 Mar 19, 2026 116 days past EOL EOL
18.8 18.8.11 Jan 15, 2026 Apr 16, 2026 88 days past EOL EOL
18.9 18.9.8 Feb 19, 2026 May 21, 2026 53 days past EOL EOL
18.10 18.10.8 Mar 19, 2026 Jun 18, 2026 25 days past EOL EOL
18.11 18.11.7 Apr 16, 2026 Jul 16, 2026 3 days remaining Warning
19.0 19.0.4 May 21, 2026 Aug 20, 2026 38 days remaining Warning
19.1 19.1.2 Jun 18, 2026 Sep 17, 2026 66 days remaining Warning

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.

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.

endoflife.ai
Get GitLab Support Options

GitLab has 61 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.

Get My Support Options →
Frequently Asked Questions
What is the end-of-life date for GitLab?
The next GitLab version reaching EOL is 18.11 on July 16, 2026. See the full table above for all version EOL dates.
When is the GitLab support end date?
The next GitLab support end date is July 16, 2026, when version 18.11 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of GitLab?
The latest active version of GitLab is . Always verify against the table above as support windows can change.
What happens when GitLab reaches end of life?
When GitLab 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 GitLab?
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 GitLab 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 →