Gerrit End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Gerrit versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.13 | 2.13.14 | Sep 21, 2016 | No EOL date | Supported | Active |
| 2.14 | 2.14.22 | Apr 26, 2017 | May 31, 2019 | 2580 days past EOL | EOL |
| 2.15 | 2.15.22 | Mar 28, 2018 | Nov 15, 2019 | 2412 days past EOL | EOL |
| 2.16 | 2.16.28 | Nov 15, 2018 | Jun 1, 2020 | 2213 days past EOL | EOL |
| 3.0 | 3.0.16 | May 15, 2019 | Dec 1, 2020 | 2030 days past EOL | EOL |
| 3.1 | 3.1.16 | Nov 14, 2019 | May 19, 2021 | 1861 days past EOL | EOL |
| 3.2 | 3.2.14 | Jun 1, 2020 | Dec 7, 2021 | 1659 days past EOL | EOL |
| 3.3 | 3.3.11 | Dec 1, 2020 | May 24, 2022 | 1491 days past EOL | EOL |
| 3.4 | 3.4.8 | May 17, 2021 | Nov 9, 2022 | 1322 days past EOL | EOL |
| 3.5 | 3.5.6 | Dec 6, 2021 | May 19, 2023 | 1131 days past EOL | EOL |
| 3.6 | 3.6.8 | May 23, 2022 | Nov 25, 2023 | 941 days past EOL | EOL |
| 3.7 | 3.7.9 | Nov 9, 2022 | May 17, 2024 | 767 days past EOL | EOL |
| 3.8 | 3.8.10 | May 19, 2023 | Dec 2, 2024 | 568 days past EOL | EOL |
| 3.9 | 3.9.11 | Nov 25, 2023 | May 19, 2025 | 400 days past EOL | EOL |
| 3.10 | 3.10.9 | May 17, 2024 | Nov 10, 2025 | 225 days past EOL | EOL |
| 3.11 | 3.11.11 | Dec 2, 2024 | May 15, 2026 | 39 days past EOL | EOL |
| 3.12 | 3.12.8 | May 19, 2025 | TBD | Supported | Active |
| 3.13 | 3.13.7 | Nov 10, 2025 | TBD | Supported | Active |
| 3.14 | 3.14.1 | May 15, 2026 | TBD | Supported | Active |
What does Gerrit end of life mean for your organization?
When a version of Gerrit 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 Gerrit 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 Gerrit versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →