GitHub Enterprise Server · Lifecycle Status

GitHub Enterprise Server End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all GitHub Enterprise Server versions. Dates read at the vendor's own lifecycle pages (docs.github.com). Updated at every deploy.

⚡ GitHub Enterprise Server 3.19 reaches end of life on December 9, 2026. Plan your migration now — 21 days remaining.

GitHub Enterprise Server 3.22 is supported until September 8, 2027, its end-of-support date. The next GitHub Enterprise Server version to reach end of life is 3.19, on December 9, 2026. 43 of 47 tracked GitHub Enterprise Server versions are past end of life; the most recent to reach it, 3.18, did so on October 16, 2026. The full GitHub Enterprise Server 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 ↓
📅 Get reminded before GitHub Enterprise Server 3.19 reaches EOL on December 9, 2026 — alerts 90, 30 & 7 days out.
Google → Subscribe to all dates
Subscribe keeps every GitHub Enterprise Server end date in your calendar and updates itself. Calendar URL: https://endoflife.ai/calendar/github-enterprise-server.ics
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
Automating this check? GET https://api.endoflife.ai/v1/score/github-enterprise-server/3.19 returns this version's end-of-life date, its source and the EOL Risk Score as JSON. Get a free API key (150 requests a day, no expiry).
Latest Active
3.22
3.22 series
Next EOL
3.19
Dec 9, 2026
Active Versions
2
of 47 total
EOL Versions
43
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 →
CPE Identifier
cpe:2.3:a:github:enterprise_server
The Common Platform Enumeration name vulnerability scanners and CVE records use for GitHub Enterprise Server. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 201520162017201820192020202120222023202420252026202711.10.3402.02.12.22.32.42.52.62.72.82.92.102.112.122.132.142.152.162.172.182.192.202.212.223.03.13.23.33.43.53.63.73.83.93.103.113.123.133.143.153.163.173.183.193.203.213.22TODAY
43 versions of GitHub Enterprise Server are past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
11.10.340 — Jul 7, 2014 Jul 7, 2015 4152 days past EOL EOL
2.0 — Nov 11, 2014 Feb 9, 2016 3935 days past EOL EOL
2.1 — Jan 20, 2015 Apr 26, 2016 3858 days past EOL EOL
2.2 — Apr 29, 2015 Aug 3, 2016 3759 days past EOL EOL
2.3 — Aug 3, 2015 Nov 1, 2016 3669 days past EOL EOL
2.4 — Oct 13, 2015 Feb 9, 2017 3569 days past EOL EOL
2.5 — Feb 9, 2016 Mar 14, 2017 3536 days past EOL EOL
2.6 — Apr 26, 2016 Apr 26, 2017 3493 days past EOL EOL
2.7 — Aug 3, 2016 Aug 3, 2017 3394 days past EOL EOL
2.8 — Nov 9, 2016 Nov 9, 2017 3296 days past EOL EOL
2.9 — Mar 1, 2017 Mar 1, 2018 3184 days past EOL EOL
2.10 — Jun 5, 2017 Jun 5, 2018 3088 days past EOL EOL
2.11 — Sep 13, 2017 Sep 13, 2018 2988 days past EOL EOL
2.12 — Dec 12, 2017 Dec 12, 2018 2898 days past EOL EOL
2.13 — Mar 27, 2018 Mar 27, 2019 2793 days past EOL EOL
2.14 — Jul 12, 2018 Jul 12, 2019 2686 days past EOL EOL
2.15 — Oct 16, 2018 Oct 16, 2019 2590 days past EOL EOL
2.16 — Jan 22, 2019 Jan 22, 2020 2492 days past EOL EOL
2.17 — May 23, 2019 May 23, 2020 2370 days past EOL EOL
2.18 — Aug 20, 2019 Aug 20, 2020 2281 days past EOL EOL
2.19 — Nov 12, 2019 Nov 12, 2020 2197 days past EOL EOL
2.20 — Feb 11, 2020 Mar 2, 2021 2087 days past EOL EOL
2.21 — Jun 9, 2020 Jun 9, 2021 1988 days past EOL EOL
2.22 — Sep 23, 2020 Sep 23, 2021 1882 days past EOL EOL
3.0 — Feb 16, 2021 Feb 16, 2022 1736 days past EOL EOL
3.1 — Jun 3, 2021 Jun 30, 2022 1602 days past EOL EOL
3.2 — Sep 28, 2021 Oct 12, 2022 1498 days past EOL EOL
3.3 — Dec 7, 2021 Jan 18, 2023 1400 days past EOL EOL
3.4 — Mar 15, 2022 Mar 23, 2023 1336 days past EOL EOL
3.5 — May 31, 2022 Jun 29, 2023 1238 days past EOL EOL
3.6 — Aug 16, 2022 Sep 25, 2023 1150 days past EOL EOL
3.7 — Nov 8, 2022 Jan 4, 2024 1049 days past EOL EOL
3.8 — Mar 7, 2023 Mar 26, 2024 967 days past EOL EOL
3.9 — Jun 29, 2023 Jul 26, 2024 845 days past EOL EOL
3.10 — Aug 29, 2023 Sep 25, 2024 784 days past EOL EOL
3.11 — Dec 5, 2023 Dec 19, 2024 699 days past EOL EOL
3.12 — Mar 5, 2024 Apr 3, 2025 594 days past EOL EOL
3.13 — Jun 18, 2024 Jun 19, 2025 517 days past EOL EOL
3.14 — Aug 27, 2024 Apr 23, 2026 209 days past EOL EOL
3.15 — Dec 3, 2024 Apr 23, 2026 209 days past EOL EOL
3.16 — Mar 11, 2025 Jul 1, 2026 140 days past EOL EOL
3.17 — Jun 3, 2025 Sep 24, 2026 55 days past EOL EOL
3.18 — Oct 14, 2025 Oct 16, 2026 33 days past EOL EOL
3.19 — Dec 9, 2025 Dec 9, 2026 21 days remaining Warning
3.20 — Mar 17, 2026 Mar 17, 2027 119 days remaining Warning
3.21 — Jun 11, 2026 Jun 11, 2027 205 days remaining Active
3.22 — Sep 8, 2026 Sep 8, 2027 294 days remaining Active
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
GitHub Enterprise Server EOL status badge Live EOL badge for your README — updates automatically at every build. [![GitHub Enterprise Server EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fgithub-enterprise-server.json)](https://endoflife.ai/github-enterprise-server)

GitHub Enterprise Server lifecycle status — the real story

GitHub Enterprise Server is the self-hosted edition of GitHub, run as an appliance on a company's own infrastructure. GitHub ships feature releases, which it says typically occur quarterly and each begin with at least one release candidate, and more frequent patch releases between them.

GitHub's releases page states that it supports at least the four most recent feature releases, and prints a release day and a closing down date for every feature release back to the first one. This page serves those two days exactly as GitHub prints them; the closing down date is not a fixed interval after the release day, so no end date here is computed.

GitHub keeps the documentation for unsupported versions online but does not maintain or update it. Its releases table marks each feature release as Supported or Not supported.

GitHub Enterprise Server release and support pattern

Across the 47 release lines with a published release date, GitHub Enterprise Server has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 1 year from its release to its end-of-life date.

Of the 47 release lines tracked, 43 are past end of life and 4 are still within support. The newest line, 3.22, was released September 8, 2026. The next scheduled end of life is 3.19 on December 9, 2026 — 21 days from this build. The longest-supported line currently published is 3.22, to September 8, 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 GitHub Enterprise Server end of life mean for your organization?

When a version of GitHub Enterprise Server reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.

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 the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL GitHub Enterprise Server 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 GitHub Enterprise Server 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.

OptionBest whenWatch 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 GitHub Enterprise Server version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get GitHub Enterprise Server Support Options

GitHub Enterprise Server has 43 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 GitHub Enterprise Server 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."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for GitHub Enterprise Server?
The next GitHub Enterprise Server version reaching EOL is 3.19 on December 9, 2026. See the full table above for all version EOL dates.
When is the GitHub Enterprise Server support end date?
The next GitHub Enterprise Server support end date is December 9, 2026, when version 3.19 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 GitHub Enterprise Server?
The latest active version of GitHub Enterprise Server is 3.22. Always verify against the table above as support windows can change.
What happens when GitHub Enterprise Server reaches end of life?
When GitHub Enterprise Server reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of GitHub Enterprise Server?
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 GitHub Enterprise Server versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

✓ 94 of 94 lifecycle dates vendor-sourced · read from GitHub (Enterprise Server releases) on 2026-11-18 · confidence: 94 high, 0 medium, 0 low (each version page shows where every date comes from) · provenance · Source: the vendor's own lifecycle pages (docs.github.com) · Generated at build time · How we source data →
GitHub Enterprise Server end-of-life status badge