Oracle JDK 21's Free Updates Ended: What Java Teams Must Do Before Oct 20

There is a date sitting eight days in front of you, and most Java teams have not put it in their calendar. On October 20, 2026, Oracle ships its quarterly Critical Patch Update. For JDK 21, that release is the first one published under the Java SE OTN license — the paid terms that already cover Java 8, 11, and 17. If you run Oracle's own JDK 21 binaries in production, this post is your checklist.

What actually changed

Oracle JDK 21 shipped in September 2023 under the No-Fee Terms and Conditions (NFTC) license, which permits free use — even commercial and production use. Oracle's stated policy: the current LTS stays under NFTC, and the previous LTS transitions to the OTN license one year after the next LTS release. JDK 25 arrived in September 2025, so JDK 21's free window ran through September 2026. Oracle's own licensing FAQ says updates after that are planned under the Java SE OTN license, the same paid terms governing Java 8, 11, and 17 today.

Two clarifications that matter:

  1. Builds you already installed do not suddenly become unlicensed. The practical issue is new security patches: from the October 2026 CPU onward, Oracle JDK 21 patches ship with a paid subscription attached for commercial production use.
  2. The exact cutoff is read slightly differently by different sources. Azul's read is that the last free JDK 21 update shipped in July 2026; others, citing Oracle, say updates through the September 2026 release stay under NFTC and October is the first OTN one. Check Oracle's current licensing FAQ for your own case — and don't treat this post as legal advice.

The silent trap: floating base images

The license change does not arrive as an email or a popup. It arrives as a build number. If your Dockerfiles, base images, or package managers pull an unpinned oracle-jdk:21 from a URL that never changes, the patch job that runs on October 21 will silently install an OTN-licensed binary into production:

# Floating tag — silently becomes OTN-licensed on Oct 20
FROM oracle-jdk:21

# Pinned — stays under NFTC terms, but gets no new security patches
FROM oracle-jdk:21.0.12

Oracle's Java SE Subscription is priced per employee, so one OTN-licensed binary running in production is enough to put your organization in licensing scope. The fix is an audit before October 20, not a panic after.

First, find out what JDK you're actually running

On every machine, CI agent, and container base image, run:

java -version

Look at the vendor line. Eclipse Adoptium / Temurin, Amazon Corretto, or Azul Zulu mean you are on a free OpenJDK distribution and this whole post is informational only. If the vendor says Oracle Corporation and the version is 21, you are in scope.

Your four options

1. Pay for a Java SE Subscription. Straightforward if you want Oracle's binaries with security patches and support. Expensive at scale — price it before October 20 rather than discovering the invoice later.

2. Upgrade to JDK 25. The current LTS is under NFTC through September 2028. If your code already runs cleanly on 21, the jump to 25 is a real option — but test first; "it's just an LTS" is not a migration plan.

3. Switch to a free OpenJDK distribution. Temurin, Corretto, Zulu, and others ship free JDK 21 builds with their own patch cadence. For most teams this is the lowest-friction exit: same Java, different vendor, no subscription. Verify your vendor's update policy before committing.

4. Pin at 21.0.12 and stay. Permissible — your existing installs remain licensed as they are. But you will not receive new security patches for Oracle's JDK 21, and the gap compounds every quarter. This is a deliberate risk decision, not a default.

The checklist for this week

  1. Audit every place a JDK enters your estate: Dockerfile base images, CI agents, developer laptops, package-manager installs.
  2. Run java -version on each and note the vendor.
  3. Pin any floating Oracle JDK 21 references — decide the long-term option separately, but stop the silent upgrade now.
  4. Confirm the decision with your licensing or legal team before October 20.

Bottom line: nothing you have installed breaks on October 20. What breaks is the assumption that the next patch is free. Eight days is enough time to audit and pin — it is not enough time to discover this from an invoice.

Comments

Popular posts from this blog

What are the core classes and interfaces of hibernate 4

JSP Servlet Interview Questions For Freshers Series 1

Java Banking Finance Services and Insurance (BFSI) domain interview questions