Runtime
Oracle
Oracle JDK 27, a non-LTS feature release that shipped on 15 September 2026, reaches end of life on 31 March 2027 — after which it receives no further Oracle updates, including security patches, and developers are expected to move to the next release or to an LTS line
departs 31 Mar 2027
Quick answers
- Is it true that Oracle JDK 27 reaches end of life on 31 March 2027 — a six-month non-LTS release?
- Yes. Oracle has officially announced it, effective 31 Mar 2027. Oracle JDK 27 is a non-LTS feature release: it shipped on 15 September 2026 and Oracle's free updates for it end on 31 March 2027, when the next feature release (JDK 28) arrives.
- When does it take effect?
- 31 Mar 2027. Verified against the vendor's own announcement.
- What should I use instead?
- For anything long-lived, run on an Oracle JDK LTS release rather than a non-LTS one.
What this means for you
Oracle JDK 27 is a non-LTS feature release: it shipped on 15 September 2026 and Oracle's free updates for it end on 31 March 2027, when the next feature release (JDK 28) arrives. That six-month window is the standard cadence for non-LTS JDKs — Oracle ships a feature release every March and September, and only every fourth one is a Long-Term-Support version. After 31 March 2027 there are no further Oracle updates for 27, including security patches; you are expected to have moved to JDK 28 or to sit on an LTS release instead. The practical risk is treating a non-LTS JDK like a stable target: a service pinned to JDK 27 in production is on a runtime that stops getting security fixes at the end of Q1 2027. For long-lived applications the right target is an LTS release — JDK 25 (supported to September 2030) or JDK 21 (September 2028) — rather than following each six-month feature release.
Where to go
For anything long-lived, run on an Oracle JDK LTS release rather than a non-LTS one. JDK 25 is the current LTS, with Oracle updates through September 2030; JDK 21 is the previous LTS, through September 2028. Both give years of patches instead of six months. If you deliberately track the latest features on the non-LTS train, plan to move from 27 to 28 promptly when 28 ships in March 2027, and keep doing so every six months — a non-LTS JDK is only safe if it is upgraded continuously. Note that these dates are for Oracle's JDK builds specifically; other distributions (Eclipse Temurin/Adoptium, Amazon Corretto, Azul, Microsoft Build of OpenJDK) publish their own support timelines, so if you run one of those, check its schedule rather than assuming Oracle's dates apply.
- Oracle JDK 25 (LTS) — Oracle updates through September 2030, the longest runway
- Oracle JDK 21 (LTS) — Oracle updates through September 2028
- A non-Oracle OpenJDK distribution (Eclipse Temurin, Amazon Corretto, Azul, Microsoft) with its own LTS support timeline
Oracle JDK 27 reaches end of life on 31 March 2027. It shipped on 15 September 2026, which makes its Oracle-updates window about six months — the standard lifespan of a non-LTS feature release.
Oracle ships a JDK feature release every March and September, and only every fourth one is a Long-Term-Support version. JDK 27 is not one of them. When JDK 28 arrives in March 2027, Oracle’s free updates for 27 stop — no further patches, including security fixes. The expectation is that you either follow the feature train to 28 or, for anything you intend to run for a while, sit on an LTS release.
The risk is treating a non-LTS JDK as a stable target. A production service pinned to JDK 27 is on a runtime that stops receiving security updates at the end of Q1 2027. For long-lived applications, the right home is an LTS line: JDK 25, with Oracle updates through September 2030, or JDK 21, through September 2028 — years of patches rather than months.
Two practical notes. If you deliberately track the latest features, plan to move from 27 to 28 promptly in March 2027 and keep upgrading every six months; a non-LTS JDK is only safe if it’s continuously updated. And these dates apply to Oracle’s JDK builds specifically — other OpenJDK distributions (Eclipse Temurin, Amazon Corretto, Azul, the Microsoft Build of OpenJDK) set their own support timelines, so if you run one of those, check its schedule rather than assuming Oracle’s.
Entry changelog
- — last reviewed.
- — Entry created from the Oracle JDK release-lifecycle data on endoflife.date, which records JDK 27 (released 15 September 2026) as a non-LTS release with end of life on 31 March 2027, alongside the LTS lines JDK 25 (EOL September 2030) and JDK 21 (EOL September 2028). Date recorded exactly as listed. No detect: fingerprint — a JDK version pinned in build config or a base image is not reliably attributable to Oracle's specific JDK builds versus other OpenJDK distributions with different support dates, so a fingerprint would risk a false alarm.
Put this countdown in your README
Building on Oracle? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/oracle-jdk-27-end-of-life)Spot an error or a changed date? Tell us and it’s corrected the same night.