OpenJDK builds from Oracle 11 · Version Status
OpenJDK builds from Oracle 11 End of Life Date
OpenJDK builds from Oracle 11 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 11 is past end of life. This version no longer receives security patches. 2790 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 19, 2019
2790 days past EOL
Latest Release
11.0.2
Standard release
Release Date
Sep 25, 2018
OpenJDK builds from Oracle 11 series
Where these dates come from
End of lifeMar 19, 2019endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseSep 25, 2018endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees 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 11 was released on September 25, 2018 and support ended on March 19, 2019 — a supported lifespan of 6 months, in line with the 6 months median for OpenJDK builds from Oracle releases. Its latest release on record is 11.0.2, published January 15, 2019 — 2 months before support ended. It has been past its end-of-life date for 7 years and 8 months. 15 newer OpenJDK builds from Oracle releases have shipped since.
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 11 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 11 end of life mean?
When OpenJDK builds from Oracle 11 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 11 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 11 reach end of life?
OpenJDK builds from Oracle 11 reached end of life on March 19, 2019. This version is no longer receiving security patches.
Is OpenJDK builds from Oracle 11 still supported?
No. OpenJDK builds from Oracle 11 reached end of life on March 19, 2019 and is no longer receiving security patches.
What should I upgrade to from OpenJDK builds from Oracle 11?
What are the security risks of running OpenJDK builds from Oracle 11 past EOL?
Since OpenJDK builds from Oracle 11 reached end of life, the maintainers no longer issue 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.