GitHub Enterprise Server 3.10 · Version Status
GitHub Enterprise Server 3.10 End of Life Date
GitHub Enterprise Server 3.10 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (docs.github.com); the source of each date is on the product page.
⚠
GitHub Enterprise Server 3.10 is past end of life. This version no longer receives security patches. 784 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 25, 2024
784 days past EOL
Latest Release
—
Standard release
Release Date
Aug 29, 2023
GitHub Enterprise Server 3.10 series
Where these dates come from
End of lifeSep 25, 2024Vendor's own page, read by our adapter · docs.github.com · checked Nov 18, 2026high · 2 sources agree ReleaseAug 29, 2023Vendor's own page, read by our adapter · docs.github.com · checked Nov 18, 2026high · 2 sources agree
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
GitHub Enterprise Server 3.10 was released on August 29, 2023 and support ended on September 25, 2024 — a supported lifespan of 1 year and 1 month, in line with the 1 year median for GitHub Enterprise Server releases. It has been past its end-of-life date for 2 years and 2 months. 8 newer GitHub Enterprise Server releases have shipped since.
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 → ·
View score card →
Extended Support
Extended GitHub Enterprise Server 3.10 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All GitHub Enterprise Server Versions
| Version | Latest | EOL Date | Status |
| 11.10.340 |
— |
Jul 7, 2015 |
EOL |
| 2.0 |
— |
Feb 9, 2016 |
EOL |
| 2.1 |
— |
Apr 26, 2016 |
EOL |
| 2.2 |
— |
Aug 3, 2016 |
EOL |
| 2.3 |
— |
Nov 1, 2016 |
EOL |
| 2.4 |
— |
Feb 9, 2017 |
EOL |
| 2.5 |
— |
Mar 14, 2017 |
EOL |
| 2.6 |
— |
Apr 26, 2017 |
EOL |
What does GitHub Enterprise Server 3.10 end of life mean?
When GitHub Enterprise Server 3.10 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running GitHub Enterprise Server 3.10 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to GitHub Enterprise Server 3.22 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does GitHub Enterprise Server 3.10 reach end of life?
GitHub Enterprise Server 3.10 reached end of life on September 25, 2024. This version is no longer receiving security patches.
Is GitHub Enterprise Server 3.10 still supported?
No. GitHub Enterprise Server 3.10 reached end of life on September 25, 2024 and is no longer receiving security patches.
What should I upgrade to from GitHub Enterprise Server 3.10?
The recommended upgrade from GitHub Enterprise Server 3.10 is
GitHub Enterprise Server 3.22 — the latest actively supported version. Check the
GitHub Enterprise Server full timeline for all supported versions.
What are the security risks of running GitHub Enterprise Server 3.10 past EOL?
Since GitHub Enterprise Server 3.10 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL GitHub Enterprise Server should migrate immediately or implement compensating controls.