OpenJDK builds from Oracle 27 · Version Status
OpenJDK builds from Oracle 27 End of Life Date
OpenJDK builds from Oracle 27 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚡
OpenJDK builds from Oracle 27 reaches end of life on March 23, 2027. Plan your migration now — 140 days remaining.
📅 Get reminded before OpenJDK builds from Oracle 27 reaches EOL on March 23, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Mar 23, 2027
140 days remaining
Latest Release
27
Standard release
Release Date
Sep 15, 2026
OpenJDK builds from Oracle 27 series
Where these dates come from
End of lifeMar 23, 2027Vendor's own page, checked by a person · jdk.java.net · checked Sep 24, 2026high · 2 sources agree ReleaseSep 15, 2026Vendor's own page, checked by a person · jdk.java.net · checked Sep 24, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
OpenJDK builds from Oracle 27 was released on September 15, 2026 and support is scheduled to end on March 23, 2027 — a planned supported lifespan of 6 months, in line with the 6 months median for OpenJDK builds from Oracle releases. Its most recent patch is 27, published September 15, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended OpenJDK builds from Oracle 27 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All OpenJDK builds from Oracle Versions
| Version | Latest | EOL Date | Status |
|---|
| 9 |
9.0.4 |
Mar 20, 2018 |
EOL |
| 10 |
10.0.2 |
Sep 25, 2018 |
EOL |
| 11 |
11.0.2 |
Mar 19, 2019 |
EOL |
| 12 |
12.0.2 |
Sep 17, 2019 |
EOL |
| 13 |
13.0.2 |
Mar 17, 2020 |
EOL |
| 14 |
14.0.2 |
Sep 16, 2020 |
EOL |
| 15 |
15.0.2 |
Mar 16, 2021 |
EOL |
| 16 |
16.0.2 |
Sep 14, 2021 |
EOL |
What does OpenJDK builds from Oracle 27 end of life mean?
When OpenJDK builds from Oracle 27 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running OpenJDK builds from Oracle 27 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does OpenJDK builds from Oracle 27 reach end of life?
OpenJDK builds from Oracle 27 reaches end of life on March 23, 2027. That is 140 days remaining.
Is OpenJDK builds from Oracle 27 still supported?
OpenJDK builds from Oracle 27 is still supported but approaching end of life on March 23, 2027. Begin planning your migration now.
What should I upgrade to from OpenJDK builds from Oracle 27?
What are the security risks of running OpenJDK builds from Oracle 27 past EOL?
When OpenJDK builds from Oracle 27 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL OpenJDK builds from Oracle should migrate immediately or implement compensating controls.