Complete end-of-life dates, support windows, and security status for all Gradle versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.12.0 | Jun 12, 2012 | Jul 1, 2014 | 4330 days past EOL | EOL |
| 2 | 2.14.1 | Jul 1, 2014 | Aug 15, 2016 | 3554 days past EOL | EOL |
| 3 | 3.5.1 | Aug 15, 2016 | Jun 14, 2017 | 3251 days past EOL | EOL |
| 4 | 4.10.3 | Jun 14, 2017 | Nov 26, 2018 | 2721 days past EOL | EOL |
| 5 | 5.6.4 | Nov 23, 2018 | Nov 8, 2019 | 2374 days past EOL | EOL |
| 6 | 6.9.4 | Nov 8, 2019 | Feb 10, 2023 | 1184 days past EOL | EOL |
| 7 | 7.6.6 | Apr 9, 2021 | Jul 31, 2025 | 282 days past EOL | EOL |
| 8 | 8.14.5 | Feb 10, 2023 | Already EOL | Supported | Active |
| 9 | 9.5.0 | Jul 31, 2025 | Already EOL | Supported | Active |
When a Gradle version 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 Gradle 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →