Oracle JDK 24 EOL Sept 16, 2025 – 3 Options to Consider

The Clock Is Ticking on Oracle JDK 24

Oracle JDK 24 reaches end of life on September 16, 2025. As a non‑Long‑Term Support (non‑LTS) release, it will receive no further public updates or security patches after that date. The latest version in the 24 line is 24.0.2, and the nine‑month runway is enough to plan and execute any of the three realistic paths.

This article compares each option honestly — cost, risk, timeline, and the environments where each makes the most sense. A short decision checklist at the end helps you pick the right path for your workload.

Lifecycle source: endoflife.date/oracle-jdk

The Three Paths for Oracle JDK 24

1. Migrate / Upgrade to a Supported JDK

What it is – Move your applications to a newer JDK release that is still under active support from Oracle. The most common target is an LTS release (e.g., JDK 21 or, when available, JDK 25), but you could also move to a newer non‑LTS release that has a later EOL date.

Cost profile – Medium to high. Licensing is free for Oracle JDK if you stay within the NFTC terms, but the real cost is engineering time for migration, regression testing, and potential code changes caused by removed APIs or behavioral differences.

Risk – Moderate to high. Non‑LTS releases can contain significant changes that may break existing code, especially with Java’s new six‑month cadence. Migration from JDK 24 to another non‑LTS might be less disruptive than jumping several versions, but you still need thorough testing.

Timeline – 2–6 months for a well‑tested migration, depending on application complexity and test automation coverage. The nine‑month window is comfortable for most teams.

Suitable for – Platforms under active development where teams can absorb refactoring cost and benefit from the latest language features or performance improvements.

2. Vendor Extended Support (Oracle)

What it is – Oracle offers Java SE Subscription / Java SE Desktop Subscription, but for non‑LTS releases like JDK 24, Oracle does not provide extended support. The only patches available after EOL are those included in the latest update (24.0.2). No security fixes or bug patches will be issued after September 16, 2025.

Verdict – This path is effectively unavailable for JDK 24. If you need to stay on this exact version beyond EOL, you cannot buy extended coverage from Oracle. The vendor page at 3rd Party Support - Oracle software lists Oracle’s current support policies for its products.

Cost profile – Not applicable (option does not exist).

3. Third‑Party Maintenance and Support

What it is – Engage a third‑party vendor (such as 3rd Party Support) to deliver custom patches, security hotfixes, and technical support for Oracle JDK 24 after Oracle stops. This is a maintenance‑only path — you get the fixes you need, not every new feature.

Cost profile – Low to moderate. Typically a fixed annual fee based on the number of instances or nodes, with no per‑seat license costs. Predictable budgeting.

Risk – Low to moderate. Because third‑party support is reactive and focused on keeping your existing JDK version running, you avoid migration risk entirely. The risk is that you must rely on a third party to backport security fixes, which they do using their own engineering teams. Reputable providers have a proven track record.

Timeline – Can be activated immediately. No code changes required. Your team can shift focus from migration to other priorities.

Suitable for – Stable workloads that just need to keep running. Ideal for legacy applications, embedded systems, or environments where certification / qualification makes upgrading costly or impossible.

Decision Checklist

Use this checklist to determine which path fits your situation.

Criterion	Migrate / Upgrade	Vendor Extended Support	Third‑Party Support
JDK 24 covered after Sep 16, 2025?	No (moving off 24)	No (not offered by Oracle)	Yes
Cost	Med‑High (dev time)	N/A	Low‑Medium (fixed fee)
Security patches	Via new JDK	None	Custom backports
Code changes required?	Yes	N/A	No
Best for	Active development	Not available	Stable / certified environments
Timeline to implement	2–6 months	N/A	Days / weeks

Next Steps

For most teams running JDK 24 on stable production systems, the most practical path is third‑party support — it eliminates migration risk, keeps your environment unchanged, and provides the security coverage the vendor no longer offers. If your application is under active development and you are willing to invest in testing, migrating to an LTS release is a strong long‑term strategy.

Contact us to discuss how third‑party maintenance can extend the life of your Oracle JDK 24 deployment safely and cost‑effectively — get in touch.