Over the past 18 months, thousands of companies have received audit notices from Oracle about unlicensed Java installations. If you manage IT infrastructure at a company with 20+ staff, this matters to you.
The Problem
On September 20, 2026, Oracle JDK 21 moved from free (NFTC) to paid (OTN) licensing. If your company auto-updates Java on employee machines, any Oracle JDK 21 installed after the September update may trigger audit notices—even if nobody is actively using it.
Which Versions Are Free?
Free (no audit risk):
- OpenJDK (GPL + Classpath Exception)
- Eclipse Temurin (Eclipse Foundation)
- Amazon Corretto (AWS-supported, free LTS)
- Azul Zulu Community Edition
- Oracle JDK 8 up to build 8u202 (January 2022)
Paid (audit risk):
- Oracle JDK 8 after build 8u202
- Oracle JDK 11, 17 (OTN-only after Sept 2026)
- Oracle JDK 21 (free until Sept 2026, then OTN-paid)
- Oracle JDK 22+ (OTN-paid immediately)
5-Step Audit You Can Run Right Now
- Find all Java installations on your fleet
- Extract vendor, version, and build number
- Cross-check the license against the roadmap
- Triage machines with paid versions
- Plan your replacement strategy
You're not doing anything wrong by having Java installed. The problem is that Oracle changed the licensing mid-year. Thousands of companies are in the same situation. Use this moment to clean up your Java footprint and move to free, well-maintained alternatives.
If you receive an audit notice from Oracle, consult your legal team. But first, knowing which machines have which Java versions is the first step to being in control.

