Microsoft Build of OpenJDK End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Microsoft Build of OpenJDK versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
✓Microsoft Build of OpenJDK 25.0.3 is actively supported. Next EOL: version 17 on September 30, 2027.
📅 Get reminded before Microsoft Build of OpenJDK 17 reaches EOL on September 30, 2027 — alerts 90, 30 & 7 days out.
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 →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
11 LTS
11.0.31
Jan 21, 2019
Sep 30, 2027
464 days remaining
Active
17 LTS
17.0.19
Sep 14, 2021
Sep 30, 2027
464 days remaining
Active
21 LTS
21.0.11
Sep 19, 2023
Sep 30, 2028
830 days remaining
Active
25 LTS
25.0.3
Sep 16, 2025
Sep 30, 2030
1560 days remaining
Active
What does Microsoft Build of OpenJDK end of life mean for your organization?
When a version of Microsoft Build of OpenJDK reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Microsoft Build of OpenJDK should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Microsoft Build of OpenJDK versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
What is the end-of-life date for Microsoft Build of OpenJDK?
The next Microsoft Build of OpenJDK version reaching EOL is 17 on September 30, 2027. See the full table above for all version EOL dates.
When is the Microsoft Build of OpenJDK support end date?
The next Microsoft Build of OpenJDK support end date is September 30, 2027, when version 17 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Microsoft Build of OpenJDK?
The latest active version of Microsoft Build of OpenJDK is 25.0.3. Always verify against the table above as support windows can change.
What happens when Microsoft Build of OpenJDK reaches end of life?
When Microsoft Build of OpenJDK reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Microsoft Build of OpenJDK?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Microsoft Build of OpenJDK versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.