Oracle GraalVM 24 · Version Status
Oracle GraalVM 24 End of Life Date
Oracle GraalVM 24 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.
⚠
Oracle GraalVM 24 is past end of life. This version no longer receives security patches. 403 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 30, 2025
403 days past EOL
Latest Release
24.0.2
Standard release
Release Date
Mar 18, 2025
Oracle GraalVM 24 series
Where these dates come from
End of lifeSep 30, 2025endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseMar 18, 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
Oracle GraalVM 24 was released on March 18, 2025 and support ended on September 30, 2025 — a supported lifespan of 7 months, in line with the 7 months median for Oracle GraalVM releases. It was not an LTS release; Oracle GraalVM reserves longer patch windows for its LTS releases. Its latest release on record is 24.0.2, published July 15, 2025 — 3 months before support ended. It has been past its end-of-life date for 1 year and 1 month.
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 →
Extended Support
Extended Oracle GraalVM 24 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Oracle GraalVM Versions
| Version | Latest | EOL Date | Status |
|---|
| 17 LTS |
17.0.21 |
Sep 30, 2026 |
EOL |
| 20 |
20.0.2 |
Sep 19, 2023 |
EOL |
| 21 LTS |
21.0.13 |
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.3.4.1 |
EOL |
Active |
What does Oracle GraalVM 24 end of life mean?
When Oracle GraalVM 24 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 Oracle GraalVM 24 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 24 reach end of life?
Oracle GraalVM 24 reached end of life on September 30, 2025. This version is no longer receiving security patches.
Is Oracle GraalVM 24 still supported?
No. Oracle GraalVM 24 reached end of life on September 30, 2025 and is no longer receiving security patches.
What should I upgrade to from Oracle GraalVM 24?
The recommended upgrade from Oracle GraalVM 24 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 24 past EOL?
Since Oracle GraalVM 24 reached end of life, the maintainers no longer issue 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 Oracle GraalVM should migrate immediately or implement compensating controls.