Java Support Deadlines and the Oracle Licensing Trap: What Actually Runs Out, and When

By Scott Bissett  ·  Last updated: August 9, 2026  ·  Covers Oracle JDK 8–25 and OpenJDK builds

Most software has one countdown: the day security patches stop. Java running on Oracle's JDK has two — a support clock and a licensing clock — and teams that plan around only one of them routinely get caught by the other. This guide lays out both, with every support date verified against vendor lifecycle data, and the escape path that resolves the two problems at once.

Key Dates at a Glance

• Oracle JDK 25: Premier Support ends 2030-09-30; Extended Support ends 2033-09-30
• Oracle JDK 21: Premier Support ends 2028-09-30; Extended Support ends 2031-09-30
• Oracle JDK 17: Premier Support ends 2026-09-30; Extended Support ends 2029-09-30
• Oracle JDK 14: Premier Support ends 2020-09-16
• Oracle JDK 11: Premier Support ends 2023-09-30; Extended Support ends 2032-01-31
• Oracle JDK 9: Premier Support ends 2018-03-20

The support clock: which Java versions are still patched

Java ships on a release train: a new version every six months, with certain releases designated long-term support (LTS) — 8, 11, 17, 21, and 25. Almost all production Java in the world sits on an LTS. Here is where each one stands:

Read that table twice, because the pattern is the story: the free, open-source builds of Java outlive Oracle's own JDK support on every legacy LTS. Temurin 8 will still be receiving community security patches more than eight years after Oracle JDK 8 support ended. Which build of Java you run has become a bigger deal than which version.

The licensing clock: how "free Java" quietly became a subscription

The licensing side is what turns a stale runtime into a budget problem. In broad, uncontested strokes:

2019: Oracle ended free public updates of Oracle JDK 8 for commercial use. From that point, applying JDK 8 patches in a business environment generally required a paid Java SE subscription. Enormous numbers of installs kept updating anyway — many organizations simply didn't notice the terms had changed.

2021: With JDK 17, Oracle introduced the "No-Fee Terms and Conditions" (NFTC) license — Oracle JDK free again, including commercial use, but only for a window: roughly until a year after the next LTS ships. When that window closes, continued updates fall back under paid terms. Free, with an expiry date most calendars never captured.

2023: Oracle moved new subscriptions to the Java SE Universal Subscription, priced per employee — not per server, not per developer, but across an organization's entire headcount, regardless of how many actually touch Java. For a company with a handful of Java services and thousands of employees, the quote change was dramatic, and it made "a few old JDK installs somewhere" a company-wide licensing question. Oracle's terms have changed several times and can change again — verify the current terms directly before making decisions that depend on them.

2024–2026: The NFTC clock ran out, and is running out again. JDK 17's free window closed first: public updates through September 2024 were permissively licensed, and everything released from October 15, 2024 onward is under the Java SE OTN license. JDK 21 is next. Oracle's Java SE Support Roadmap states that updates of Oracle JDK 21 released beginning with the October 2026 Critical Patch Update are planned to move to the OTN license, the same license Oracle already uses for 8, 11 and 17. If you run Oracle's own JDK 21 build in production without a subscription, October 2026 is your licensing date, and it has nothing to do with Java 21's support dates. Oracle's stated remedy is Oracle JDK 25 or later, whose own permissive window the roadmap puts at updates released through September 2028.

The escape path: same Java, different build

What saves most teams is a fact that still surprises people: since Java 11, Oracle JDK and OpenJDK are built from essentially the same source code. The class files your application runs are the same platform. That means the fix is rarely "rewrite the app" — it's "swap the runtime":

1. Move to an OpenJDK build (most teams' answer)

Eclipse Temurin (from the Adoptium project) is the most widely adopted open-source build — no license fee, no audit surface, passes the same compatibility test suite. Swap the runtime, run your test suite, done. Other freely available OpenJDK builds exist as well, including Oracle's own no-cost OpenJDK builds — though those only receive updates for six months per release, so they suit teams that upgrade continuously, not teams that sit on an LTS.

2. Upgrade the version while you're at it

If you're touching the runtime anyway, land on Java 21 or 25 rather than 17 — Oracle's Premier Support for 17 ended September 30, 2026, and even Temurin 17 runs out in October 2027. If you run Oracle's own build rather than an OpenJDK one, pick 25: Oracle JDK 21 updates move to the OTN license with the October 2026 Critical Patch Update, while Oracle's roadmap keeps JDK 25 permissively licensed until updates released after September 2028. The 8-to-modern jump is the only genuinely hard one (removed internal APIs, module system); 11-to-21 and 17-to-21 are usually routine.

3. Can't move yet? Bridge it — deliberately

Some Java 8 estates are welded to vendor software that will never certify a newer runtime. For those, commercial extended-support vendors provide continued security patches for legacy Java versions — see our extended support options page. Treat it as a bridge with a migration date attached, not a destination.

What to do this quarter

Inventory first: find every JVM in the estate and identify its build (Oracle JDK vs an OpenJDK distribution) and version — java -version tells you both. Anything on Oracle JDK 8 or 11 is the priority pile: it's years unpatched and carries the licensing exposure. Anything on Oracle JDK 17 has a hard date — September 30, 2026 — to either subscribe, swap builds, or upgrade. You can check any version's current status in seconds with the EOL checker, and the rest of 2026's deadline calendar — OpenSSL 3.0, Python 3.10, .NET 8/9, PostgreSQL 14, PHP 8.2 — lives on the EOL Watch page.

Frequently Asked Questions

Related Resources

• Oracle JDK version data on endoflife.ai
• Eclipse Temurin version data
• The 2026 EOL Calendar
• Spring Framework End of Life Guide