OpenJDK builds from Oracle 16 · Version Status
OpenJDK builds from Oracle 16 End of Life Date
OpenJDK builds from Oracle 16 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 16 is past end of life. This version no longer receives security patches. 1835 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 14, 2021
1835 days past EOL
Latest Release
16.0.2
Standard release
Release Date
Mar 16, 2021
OpenJDK builds from Oracle 16 series
Lifecycle detail
OpenJDK builds from Oracle 16 was released on March 16, 2021 and support ended on September 14, 2021 — a supported lifespan of 6 months, in line with the 6 months median for OpenJDK builds from Oracle releases. The last patch it will ever receive is 16.0.2, published July 20, 2021 — 2 months before support ended. It has been without security patches for 5 years. 10 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 16 support is available
Commercial vendors offer security patches beyond EOL. 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 16 end of life mean?
When OpenJDK builds from Oracle 16 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 16 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to OpenJDK builds from Oracle 27 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does OpenJDK builds from Oracle 16 reach end of life?
OpenJDK builds from Oracle 16 reached end of life on September 14, 2021. This version is no longer receiving security patches.
Is OpenJDK builds from Oracle 16 still supported?
No. OpenJDK builds from Oracle 16 reached end of life on September 14, 2021 and is no longer receiving security patches.
What should I upgrade to from OpenJDK builds from Oracle 16?
The recommended upgrade from OpenJDK builds from Oracle 16 is
OpenJDK builds from Oracle 27 — the latest actively supported version. Check the
OpenJDK builds from Oracle full timeline for all supported versions.
What are the security risks of running OpenJDK builds from Oracle 16 past EOL?
When OpenJDK builds from Oracle 16 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.