Microsoft Build of OpenJDK 25 · Version Status
Microsoft Build of OpenJDK 25 End of Life Date
Microsoft Build of OpenJDK 25 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.
✓
Microsoft Build of OpenJDK 25 is actively supported. No end-of-life date has been announced yet.
Latest Release
25.0.5.0.3
LTS release
Release Date
Sep 16, 2025
Microsoft Build of OpenJDK 25 series
Where these dates come from
ReleaseSep 16, 2025endoflife.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
Microsoft Build of OpenJDK 25 was released on September 16, 2025 and has no published end-of-life date yet. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 25.0.5.0.3, published October 27, 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 →
All Microsoft Build of OpenJDK Versions
| Version | Latest | EOL Date | Status |
|---|
| 11 LTS |
11.0.33 |
EOL |
Active |
| 17 LTS |
17.0.21.0.3 |
EOL |
Active |
| 21 LTS |
21.0.13.0.3 |
EOL |
Active |
| → 25 LTS |
25.0.5.0.3 |
EOL |
Active |
What does Microsoft Build of OpenJDK 25 end of life mean?
When Microsoft Build of OpenJDK 25 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 Microsoft Build of OpenJDK 25 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Microsoft Build of OpenJDK 25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Microsoft Build of OpenJDK 25 reach end of life?
Microsoft Build of OpenJDK 25 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Microsoft Build of OpenJDK 25 still supported?
Yes, Microsoft Build of OpenJDK 25 is currently supported. The EOL date is TBD.
What should I upgrade to from Microsoft Build of OpenJDK 25?
The recommended upgrade from Microsoft Build of OpenJDK 25 is
Microsoft Build of OpenJDK 25 — the latest actively supported version. Check the
Microsoft Build of OpenJDK full timeline for all supported versions.
What are the security risks of running Microsoft Build of OpenJDK 25 past EOL?
When Microsoft Build of OpenJDK 25 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 Microsoft Build of OpenJDK should migrate immediately or implement compensating controls.