Complete end-of-life dates, support windows, and security status for all Graalvm Ce versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 17 | 17.0.9 | Jun 13, 2023 | Oct 24, 2023 | 928 days past EOL | EOL |
| 20 | 20.0.2 | Jun 13, 2023 | Sep 19, 2023 | 963 days past EOL | EOL |
| 21 | 21.0.2 | Sep 19, 2023 | Mar 19, 2024 | 781 days past EOL | EOL |
| 22 | 22.0.2 | Mar 19, 2024 | Sep 17, 2024 | 599 days past EOL | EOL |
| 23 | 23.0.2 | Sep 17, 2024 | Mar 18, 2025 | 417 days past EOL | EOL |
| 24 | 24.0.2 | Mar 18, 2025 | Sep 16, 2025 | 235 days past EOL | EOL |
| 25 | 25.0.2 | Sep 16, 2025 | Already EOL | Supported | Active |
When a Graalvm Ce 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 Graalvm Ce 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →