Java’s September 2026 Cliff: Nine Runtime Lines Reached End of Life in One Month
September 2026 was the busiest month on the Java lifecycle calendar in years. Nine runtime lines from seven vendors reached end of life within thirty days of each other. Six of those were routine — the non-LTS 26 series ending once JDK 27 shipped. Three were not: SapMachine 17 (September 2026; SAP prints the month only), Oracle GraalVM for JDK 17 and Oracle JDK 17 Premier Support (both September 30). JDK 17 is one of the most deployed Java versions in production, and for Oracle-distribution users its free-update era ended in September 2026.
Key Dates at a Glance
- SapMachine 17 (LTS): end of life September 2026 (SAP prints the month only)
- Eclipse Temurin 26: end of life 2026-09-22
- BellSoft Liberica 26: end of life 2026-09-16
- Oracle OpenJDK 26 builds: end of life 2026-09-15
- Oracle JDK 26: end of life 2026-09
- Azul Zulu 26: end of life 2026-09-30
- Oracle GraalVM for JDK 17: support ends 2026-09-30
- Oracle JDK 17: Premier Support ends 2026-09
- IBM Semeru 26: end of life 2026-09-30
The full September table
| Runtime line | EOL date | LTS? | What it means |
|---|---|---|---|
| SapMachine 17 | Sep 2026 (SAP prints the month) | Yes | SAP’s five-year window closed. SAP workloads move to SapMachine 21 (supported to September 2028; SAP prints the month). |
| Eclipse Temurin 26 | Sep 22, 2026 | No | Routine — ended when Temurin's 27 build shipped. Move to 27 or step onto an LTS. |
| BellSoft Liberica 26 | 2026-09-16 | No | Routine. |
| Oracle OpenJDK 26 builds | 2026-09-15 | No | Routine. |
| Oracle JDK 26 | 2026-09 | No | Routine. |
| Azul Zulu 26 | 2026-09-30 | No | Routine. |
| Oracle GraalVM for JDK 17 | 2026-09-30 | Yes | Native-image workloads on 17 need GraalVM for JDK 21 (to at least 2028-09, following Oracle JDK 21) or later. |
| Oracle JDK 17 (Premier Support) | 2026-09 | Yes | The big one. Premier Support ended; Extended Support requires an Oracle Java SE Subscription, with the Extended Support fee waived October 2026 to September 2029 per Oracle’s roadmap. See the escape routes below. |
| IBM Semeru 26 | 2026-09-30 | No | Routine. |
If you are on JDK 17: four exits, three of them free
JDK 17 itself did not die in September — Oracle’s Premier Support for it did. The OpenJDK 17 codebase keeps receiving updates, and several TCK-verified distributions ship them at no cost for years yet. Verified against each vendor’s lifecycle data:
| Option | Patched until | Cost |
|---|---|---|
| Upgrade to JDK 21 or 25 (LTS) | 21: into 2028–2030 by distro; 25: into 2030–2033 | Free |
| Switch to Eclipse Temurin 17 | Temurin 17: supported to at least 2027-10 (Adoptium minimum) | Free |
| Switch to Amazon Corretto 17 | Corretto 17: end of life 2029-10 | Free |
| Switch to Azul Zulu 17 / Microsoft OpenJDK 17 | Zulu 17: 2029-09-30 free builds; Microsoft: no earlier than September 2027 (Microsoft may extend) | Free (paid support optional) |
| Stay on Oracle JDK 17 with Extended Support | To at least September 2029 (Oracle’s roadmap says “or later”) | Java SE Subscription (paid); Oracle waives the Extended Support fee October 2026 to September 2029 |
For server-side workloads, switching OpenJDK distributions is normally a drop-in replacement: same bytecode, same class libraries, TCK-verified compatibility. The migration cost is testing, not rewriting. Which distribution fits depends on how long you intend to stay on 17 — our Java EOL dates by vendor reference compares every distribution’s window side by side.
Why so many at once?
Two independent clocks happened to strike together. The six-month OpenJDK cadence retires every vendor’s non-LTS 26 build when the next release arrives, and JDK 27 reached general availability on 2026-09-15 — that accounts for six of the nine lines and was business as usual. The LTS clock is the meaningful one: Oracle’s Premier Support policy gives each LTS five years, and JDK 17 (September 2021) hit that wall in September 2026. SAP’s five-year SapMachine window closed in September 2026 for the same underlying reason. When the most deployed LTS of its generation ages out of free vendor support at multiple vendors in the same month, the migration traffic jam was real — and for estates that have not moved yet, it still is: plan for load on your own teams, not just the date.
Which of your JVMs hit a wall in September?
Check every Java runtime you run — by distribution and version, with risk scores and verified dates.
Java lifecycle by distribution →