Oracle Graalvm 25 · Version Status

Oracle Graalvm 25 End of Life Date

Oracle Graalvm 25 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Oracle Graalvm 25 is actively supported. EOL date: September 30, 2030.
EOL Date
Sep 30, 2030
1605 days remaining
Latest Release
25.0.3
Standard release
Release Date
Sep 16, 2025
Oracle Graalvm 25 series
← Oracle Graalvm 24 All Oracle Graalvm versions
All Oracle Graalvm Versions
VersionLatestEOL DateStatus
17 LTS 17.0.19 Sep 30, 2026 Warning
20 20.0.2 Sep 19, 2023 EOL
21 LTS 21.0.11 Sep 30, 2028 Active
22 22.0.2 Sep 17, 2024 EOL
23 23.0.2 Mar 31, 2025 EOL
24 24.0.2 Sep 30, 2025 EOL
25 25.0.3 Sep 30, 2030 Active

What does Oracle Graalvm 25 end of life mean?

When Oracle Graalvm 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Oracle Graalvm 25 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Oracle Graalvm 25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Oracle Graalvm 25 reach end of life?
Oracle Graalvm 25 reached end of life on September 30, 2030. That is 1605 days remaining.
Is Oracle Graalvm 25 still supported?
Yes, Oracle Graalvm 25 is currently supported. The EOL date is September 30, 2030.
What should I upgrade to from Oracle Graalvm 25?
The recommended upgrade from Oracle Graalvm 25 is Oracle Graalvm 25 — the latest actively supported version. Check the Oracle Graalvm full timeline for all supported versions.
What are the security risks of running Oracle Graalvm 25 past EOL?
When Oracle Graalvm 25 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Oracle Graalvm should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →