Oracle JDK 17 LTS EOL September 2026 – 3 Support Paths

Oracle JDK 17 (Long-Term Support) reaches its official end of life on September 30, 2026. With approximately nine months until that date, infrastructure managers and procurement leads must decide how to handle their existing JDK 17 installations. Three realistic paths are available: migrate to a newer JDK release, purchase vendor extended support (if offered), or move to third-party support. Each carries different cost profiles, risk levels, and time commitments. This article breaks down the options so you can match the right path to your workloads.

The Deadline: What Ends on September 30, 2026

Oracle’s standard support for JDK 17, including security patches and bug fixes, ends on September 30, 2026. This applies specifically to version 17 (LTS), with the latest update being 17.0.20. After that date, Oracle will no longer release public updates for this version. Organizations running JDK 17 will need a support pathway to continue receiving critical fixes.

Option 1: Migrate to a Newer JDK Release

Cost profile: Moderate to high. Migration requires testing, potential code changes, and redeployment. If your applications depend on libraries or frameworks that are not yet compatible with the target JDK version, additional development work is needed.

Risk: Medium. The risk depends on the maturity of the target JDK and the complexity of your application portfolio. A well-tested migration on non-critical workloads carries low risk, but migrating large, monolithic systems under a tight timeline introduces a higher chance of regression.

Timeline: 3–9 months, depending on scope. Nine months is sufficient for many environments, but organizations with hundreds of applications or strict compliance requirements may need to start immediately.

Suitable environments: Applications under active development, platforms that need to adopt new language features, and teams that already have a continuous integration pipeline for JDK upgrades. This path is less suitable for legacy or stable workloads where the only requirement is continued security patching.

Option 2: Acquire Oracle Extended Support (If Available)

Cost profile: High, and often escalates annually. Oracle typically charges a premium over the standard subscription fee for extended support, and the pricing increases after the first year. Exact rates are not published here, but the general pattern is a steep cost per processor or per user.

Risk: Low, provided the contract is in place. You remain on an Oracle-supported version with direct access to vendor patches and support. However, the terms may require regular re-certifications or restrict the use of certain third-party tools.

Timeline: Immediate, as long as a contract is signed before the support end date. There is no migration effort, but the financial commitment must be approved in advance.

Suitable environments: Organizations with high compliance requirements that mandate vendor support, or those that cannot migrate in time and have budget for the premium. Not ideal for cost-constrained teams or for workloads that will eventually be decommissioned.

Option 3: Leverage Third-Party Maintenance

Cost profile: Typically 50–60% lower than Oracle extended support. With third-party support, you pay a flat annual fee that covers all updates for the supported product across your estate.

Risk: Low. Third-party maintenance providers deliver the same type of security patches and critical bug fixes as the vendor, but without forcing a version upgrade. The patches are derived from public source code and validated against the same OpenJDK codebase that Oracle uses. The risk of breaking changes is minimal because no new features or API changes are introduced.

Timeline: Usually 30 days or less to transition from vendor support. No migration effort is required; you simply continue running the same JDK 17 builds.

Suitable environments: Stable workloads that just need to keep running – legacy applications, embedded systems, or any environment where the risk and cost of migration outweigh the benefits of a newer JDK. Also ideal for organizations that want to extend the useful life of their existing hardware and software investments without recurring vendor escalations.

Decision Checklist

Use the following criteria to evaluate which path fits your environment:

• Cost sensitivity: If budget is tight, third-party maintenance is the most predictable and lowest-cost option. Oracle extended support is the most expensive over time.
• Migration readiness: If your applications are already certified on a newer JDK and you have a testing pipeline, migrating may be straightforward. If not, third-party support buys you time without risk.
• Compliance requirements: Some regulated industries require vendor support. Check whether third-party support meets your auditor’s standards (many do, but confirm with your compliance team).
• Application stability: For applications that have not changed in years and have no new feature requirements, third-party support avoids unnecessary code churn.
• Time horizon: If you plan to decommission the application within 12–18 months, third-party support is cheaper than buying extended support or investing in a migration that will not generate long-term value.

Next Steps

Oracle JDK 17 LTS is a stable, well-proven platform. The end of vendor support in September 2026 does not mean the software suddenly becomes unusable – it means you need a plan for continued security coverage. Each of the three paths can work, but the right choice depends on your specific workload characteristics and budget.

If you want to discuss how third-party support can keep your JDK 17 environments safe and compliant without breaking your roadmap, get in touch with our team. We can provide a no-obligation assessment of your current estate.

Lifecycle source: endoflife.date/oracle-jdk

Vendor page: Oracle software support options