Gradle 3 · Version Status
Gradle 3 End of Life Date
Gradle 3 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Gradle 3 is past end of life. This version no longer receives security patches. 3388 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 14, 2017
3388 days past EOL
Latest Release
3.5.1
Standard release
Release Date
Aug 15, 2016
Gradle 3 series
Lifecycle detail
Gradle 3 was released on August 15, 2016 and support ended on June 14, 2017 — a supported lifespan of 10 months, shorter than the 2 years and 1 month median for Gradle releases. The last patch it will ever receive is 3.5.1, published June 16, 2017 — 2 days after the published end-of-life date. It has been without security patches for 9 years and 3 months. 5 newer Gradle 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 Gradle 3 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.12.0 |
Jul 1, 2014 |
EOL |
| 2 |
2.14.1 |
Aug 15, 2016 |
EOL |
| → 3 |
3.5.1 |
Jun 14, 2017 |
EOL |
| 4 |
4.10.3 |
Nov 26, 2018 |
EOL |
| 5 |
5.6.4 |
Nov 8, 2019 |
EOL |
| 6 |
6.9.4 |
Feb 10, 2023 |
EOL |
| 7 |
7.6.6 |
Jul 31, 2025 |
EOL |
| 8 |
8.14.5 |
EOL |
Active |
What does Gradle 3 end of life mean?
When Gradle 3 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 Gradle 3 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Gradle 9 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Gradle 3 reach end of life?
Gradle 3 reached end of life on June 14, 2017. This version is no longer receiving security patches.
Is Gradle 3 still supported?
No. Gradle 3 reached end of life on June 14, 2017 and is no longer receiving security patches.
What should I upgrade to from Gradle 3?
The recommended upgrade from Gradle 3 is
Gradle 9 — the latest actively supported version. Check the
Gradle full timeline for all supported versions.
What are the security risks of running Gradle 3 past EOL?
When Gradle 3 reaches end of life, the maintainers stop issuing 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 Gradle should migrate immediately or implement compensating controls.