Gitlab Runner End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Gitlab Runner versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 18.0 | 18.0.0 | May 14, 2025 | Aug 21, 2025 | 339 days past EOL | EOL |
| 18.1 | 18.1.0 | Jun 18, 2025 | Sep 18, 2025 | 311 days past EOL | EOL |
| 18.2 | 18.2.0 | Jul 16, 2025 | Oct 16, 2025 | 283 days past EOL | EOL |
| 18.3 | 18.3.0 | Aug 21, 2025 | Nov 20, 2025 | 248 days past EOL | EOL |
| 18.4 | 18.4.0 | Sep 18, 2025 | Dec 18, 2025 | 220 days past EOL | EOL |
| 18.5 | 18.5.0 | Oct 16, 2025 | Jan 15, 2026 | 192 days past EOL | EOL |
| 18.6 | 18.6.6 | Nov 20, 2025 | Feb 19, 2026 | 157 days past EOL | EOL |
| 18.7 | 18.7.2 | Dec 18, 2025 | Mar 19, 2026 | 129 days past EOL | EOL |
| 18.8 | 18.8.0 | Jan 15, 2026 | Apr 16, 2026 | 101 days past EOL | EOL |
| 18.9 | 18.9.0 | Feb 19, 2026 | May 21, 2026 | 66 days past EOL | EOL |
| 18.10 | 18.10.1 | Mar 19, 2026 | Jun 18, 2026 | 38 days past EOL | EOL |
| 18.11 | 18.11.4 | Apr 16, 2026 | Jul 16, 2026 | 10 days past EOL | EOL |
| 19.0 | 19.0.2 | May 21, 2026 | Aug 20, 2026 | 25 days remaining | Warning |
| 19.1 | 19.1.1 | Jun 18, 2026 | Sep 17, 2026 | 53 days remaining | Warning |
| 19.2 | 19.2.0 | Jul 16, 2026 | Oct 20, 2026 | 86 days remaining | Warning |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/gitlab-runner)
What does Gitlab Runner end of life mean for your organization?
When a version of Gitlab Runner 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 Runner 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 Runner versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Gitlab Runner has 12 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Gitlab Runner 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.