GitLab 17.8 · Version Status
GitLab 17.8 End of Life Date
GitLab 17.8 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
GitLab 17.8 is past end of life. This version no longer receives security patches. 513 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 17, 2025
513 days past EOL
Latest Release
17.8.7
Standard release
Release Date
Jan 16, 2025
GitLab 17.8 series
Lifecycle detail
GitLab 17.8 was released on January 16, 2025 and support ended on April 17, 2025 — a supported lifespan of 3 months, in line with the 3 months median for GitLab releases. The last patch it will ever receive is 17.8.7, published April 9, 2025 — 8 days before support ended. It has been without security patches for 1 year and 5 months. 16 newer GitLab releases have shipped since.
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Named in 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 → ·
View score card →
Extended Support
Extended GitLab 17.8 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 13.10 |
13.10.5 |
Jun 22, 2021 |
EOL |
| 13.11 |
13.11.7 |
Jul 22, 2021 |
EOL |
| 13.12 |
13.12.15 |
Aug 22, 2021 |
EOL |
| 14.0 |
14.0.12 |
Sep 22, 2021 |
EOL |
| 14.1 |
14.1.8 |
Oct 22, 2021 |
EOL |
| 14.2 |
14.2.7 |
Nov 22, 2021 |
EOL |
| 14.3 |
14.3.6 |
Dec 22, 2021 |
EOL |
| 14.4 |
14.4.5 |
Jan 22, 2022 |
EOL |
What does GitLab 17.8 end of life mean?
When GitLab 17.8 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 GitLab 17.8 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does GitLab 17.8 reach end of life?
GitLab 17.8 reached end of life on April 17, 2025. This version is no longer receiving security patches.
Is GitLab 17.8 still supported?
No. GitLab 17.8 reached end of life on April 17, 2025 and is no longer receiving security patches.
What should I upgrade to from GitLab 17.8?
What are the security risks of running GitLab 17.8 past EOL?
When GitLab 17.8 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 GitLab should migrate immediately or implement compensating controls.