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 from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
GitLab Runner 19.5 is supported until January 21, 2027, its end-of-support date. Active support for GitLab Runner 19.5 ends on November 19, 2026; security fixes continue until that end-of-life date. The next GitLab Runner version to reach end of life is 19.3, on November 19, 2026. 15 of 18 tracked GitLab Runner versions are past end of life; the most recent to reach it, 19.2, did so on October 15, 2026. The full GitLab Runner lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 18.0 | 18.0.5 | May 14, 2025 | Aug 21, 2025 | 429 days past EOL | EOL |
| 18.1 | 18.1.3 | Jun 18, 2025 | Sep 18, 2025 | 401 days past EOL | EOL |
| 18.2 | 18.2.2 | Jul 16, 2025 | Oct 16, 2025 | 373 days past EOL | EOL |
| 18.3 | 18.3.1 | Aug 21, 2025 | Nov 20, 2025 | 338 days past EOL | EOL |
| 18.4 | 18.4.0 | Sep 18, 2025 | Dec 18, 2025 | 310 days past EOL | EOL |
| 18.5 | 18.5.0 | Oct 16, 2025 | Jan 15, 2026 | 282 days past EOL | EOL |
| 18.6 | 18.6.6 | Nov 20, 2025 | Feb 19, 2026 | 247 days past EOL | EOL |
| 18.7 | 18.7.2 | Dec 18, 2025 | Mar 19, 2026 | 219 days past EOL | EOL |
| 18.8 | 18.8.0 | Jan 15, 2026 | Apr 16, 2026 | 191 days past EOL | EOL |
| 18.9 | 18.9.0 | Feb 19, 2026 | May 21, 2026 | 156 days past EOL | EOL |
| 18.10 | 18.10.1 | Mar 19, 2026 | Jun 18, 2026 | 128 days past EOL | EOL |
| 18.11 | 18.11.4 | Apr 16, 2026 | Jul 16, 2026 | 100 days past EOL | EOL |
| 19.0 | 19.0.3 | May 21, 2026 | Aug 20, 2026 | 65 days past EOL | EOL |
| 19.1 | 19.1.5 | Jun 18, 2026 | Sep 17, 2026 | 37 days past EOL | EOL |
| 19.2 | 19.2.6 | Jul 16, 2026 | Oct 15, 2026 | 9 days past EOL | EOL |
| 19.3 | 19.3.3 | Aug 20, 2026 | Nov 19, 2026 | 26 days remaining | Warning |
| 19.4 | 19.4.1 | Sep 17, 2026 | Dec 17, 2026 | 54 days remaining | Warning |
| 19.5 | 19.5.1 | Oct 15, 2026 | Jan 21, 2027 | 89 days remaining | Warning |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/gitlab-runner)
GitLab Runner release and support pattern
Across the 18 release lines with a published release date, GitLab Runner has shipped a new line roughly every 4 weeks (median interval). A line typically stays supported for about 3 months from its release to its end-of-life date.
Of the 18 release lines tracked, 15 are past end of life and 3 are still within support. The newest line, 19.5, was released October 15, 2026. The next scheduled end of life is 19.3 on November 19, 2026 — 25 days from this build. The longest-supported line currently published is 19.5, to January 21, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Your options when GitLab Runner 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.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your GitLab Runner version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
GitLab Runner has 15 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for GitLab Runner is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."