Oracle Jdk 17 · Version Status
Oracle Jdk 17 End of Life Date
Oracle Jdk 17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚡
Oracle Jdk 17 reaches end of life on September 30, 2026. Plan your migration now — 144 days remaining.
EOL Date
Sep 30, 2026
144 days remaining
Latest Release
17.0.19
LTS release
Release Date
Sep 14, 2021
Oracle Jdk 17 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.2 |
May 7, 1996 |
EOL |
| 1.1 |
1.1.8_010 |
Oct 9, 2002 |
EOL |
| 1.2 |
1.2.2_18 |
Nov 30, 2003 |
EOL |
| 1.3 |
1.3.1_32 |
Mar 31, 2006 |
EOL |
| 1.4 |
1.4.2_42 |
Oct 30, 2008 |
EOL |
| 5 |
5.0u85 |
Oct 30, 2009 |
EOL |
| 6 |
6u211 |
Dec 31, 2018 |
EOL |
| 7 LTS |
7u351 |
Jul 31, 2019 |
EOL |
What does Oracle Jdk 17 end of life mean?
When Oracle Jdk 17 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Oracle Jdk 17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Oracle Jdk 25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Oracle Jdk 17 reach end of life?
Oracle Jdk 17 reached end of life on September 30, 2026. That is 144 days remaining.
Is Oracle Jdk 17 still supported?
Oracle Jdk 17 is still supported but approaching end of life on September 30, 2026. Begin planning your migration now.
What should I upgrade to from Oracle Jdk 17?
The recommended upgrade from Oracle Jdk 17 is
Oracle Jdk 25 — the latest actively supported version. Check the
Oracle Jdk full timeline for all supported versions.
What are the security risks of running Oracle Jdk 17 past EOL?
When Oracle Jdk 17 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Oracle Jdk should migrate immediately or implement compensating controls.