← ← Back to all products
Oracle GraalVM
Active
Runtimes & JDKs Latest Version: 25.0.2 Latest Release: Jan 20, 2026
Oracle GraalVM is an enterprise edition of GraalVM with additional performance optimizations and support.
Versions
7
Latest Version
25.0.2
Active Support
3
EOL
4
Lifecycle Timeline
Today ↓
25
25
24
24
23
23
22
22
21
21
20
20
17
17
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 25 | Sep 16, 2025 | - | Sep 30, 2030 | 25.0.2 | No | Active |
| 24 | Mar 18, 2025 | - | Sep 30, 2025 | 24.0.2 | No | EOL |
| 23 | Sep 17, 2024 | - | Mar 31, 2025 | 23.0.2 | No | EOL |
| 22 | Mar 19, 2024 | - | Sep 17, 2024 | 22.0.2 | No | EOL |
| 21 | Sep 19, 2023 | - | Sep 30, 2028 | 21.0.10 | Yes | Active |
| 20 | Jun 13, 2023 | - | Sep 19, 2023 | 20.0.2 | No | EOL |
| 17 | Jun 13, 2023 | - | Sep 30, 2026 | 17.0.18 | Yes | Active |
Frequently Asked Questions
Which versions of Oracle GraalVM have reached end of life?
The following Oracle GraalVM versions have reached end of life and no longer receive security updates: 24, 23, 22, 20. It is recommended to upgrade to a supported version.
Is it safe to continue using Oracle GraalVM 24?
Oracle GraalVM 24 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Oracle GraalVM?
The latest version of Oracle GraalVM is 25.0.2, released in the 25 release cycle.
How many versions of Oracle GraalVM are currently supported?
Oracle GraalVM currently has 3 actively supported version(s): 25, 21, 17.
When does Oracle GraalVM 25 reach end of life?
Oracle GraalVM 25 is scheduled to reach end of life on Sep 30, 2030.
What should I do when Oracle GraalVM reaches end of life?
When a Oracle GraalVM version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.