Microsoft Build Of Openjdk · Lifecycle Status

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 11.0.31 is actively supported. Next EOL: version 17 on September 30, 2027.
Latest Active
11.0.31
11 series
Next EOL
17
Sep 30, 2027
Active Versions
4
of 4 total
EOL Versions
0
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20192020202120222023202420252026202720282029203011172125TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
11 LTS 11.0.31 Jan 21, 2019 Sep 30, 2027 509 days remaining Active
17 LTS 17.0.19 Sep 14, 2021 Sep 30, 2027 509 days remaining Active
21 LTS 21.0.11 Sep 19, 2023 Sep 30, 2028 875 days remaining Active
25 LTS 25.0.3 Sep 16, 2025 Sep 30, 2030 1605 days remaining Active

What does Microsoft Build Of Openjdk end of life mean for your organization?

When a Microsoft Build Of Openjdk version 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
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.
What is the latest supported version of Microsoft Build Of Openjdk?
The latest active version of Microsoft Build Of Openjdk is 11.0.31. 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.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →