Oracle GraalVM · Lifecycle Status

Oracle GraalVM End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Oracle GraalVM versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.

✓ Oracle GraalVM 25.3.4.1 is actively supported. Next EOL: version 21 on September 30, 2028.

Oracle GraalVM 25 is supported, with no end-of-life or end-of-support date announced yet. The next Oracle GraalVM version to reach end of life is 21, on September 30, 2028. 5 of 7 tracked Oracle GraalVM versions are past end of life; the most recent to reach it, 17, did so on September 30, 2026. The full Oracle GraalVM lifecycle, with every version's release and end-of-support date, is in the table below.

Running an EOL version? Get matched with support options — free ↓
📅 Get reminded before Oracle GraalVM 21 reaches EOL on September 30, 2028 — alerts 90, 30 & 7 days out.
Google → Subscribe to all dates
Subscribe keeps every Oracle GraalVM end date in your calendar and updates itself. Calendar URL: https://endoflife.ai/calendar/oracle-graalvm.ics
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
Latest Active
25.3.4.1
25 series
Next EOL
21
Sep 30, 2028
Active Versions
2
of 7 total
EOL Versions
5
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
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 →
CPE Identifier
cpe:2.3:a:oracle:graalvm
The Common Platform Enumeration name vulnerability scanners and CVE records use for Oracle GraalVM. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 2024202520262027202820172122232425TODAY
5 versions of Oracle GraalVM are past end of life — standard security patches have stopped; 1 of them is still covered by Extended support. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
17 LTS 17.0.21 Jun 13, 2023 Sep 30, 2026 Sep 30, 2029
Extended support
39 days past EOL EOL
20 20.0.2 Jun 13, 2023 Sep 19, 2023 — 1146 days past EOL EOL
21 LTS 21.0.13 Sep 19, 2023 Sep 30, 2028 Sep 30, 2031
Extended support
692 days remaining Active
22 22.0.2 Mar 19, 2024 Sep 17, 2024 — 782 days past EOL EOL
23 23.0.2 Sep 17, 2024 Mar 31, 2025 — 587 days past EOL EOL
24 24.0.2 Mar 18, 2025 Sep 30, 2025 — 404 days past EOL EOL
25 25.3.4.1 Sep 16, 2025 TBD — Supported Active
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
EOL date vs extended support. The EOL Date column is the end of standard, included support. Extended support terms vary by vendor. Check whether the programme covers you before relying on these dates. 1 version of Oracle GraalVM is past the standard EOL date but still inside the extended support window.
Oracle GraalVM EOL status badge Live EOL badge for your README — updates automatically at every build. [![Oracle GraalVM EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Foracle-graalvm.json)](https://endoflife.ai/oracle-graalvm)

Oracle GraalVM release and support pattern

Across the 7 release lines with a published release date, Oracle GraalVM has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 6 months from its release to its standard-support end date (measured on the 6 lines with both dates published). 2 of the 7 tracked lines are designated long-term support, which is where the longer windows sit.

Of the 7 release lines tracked, 5 are past end of life and 2 are still within support. The newest line, 25, was released September 16, 2025. The next scheduled end of life is 21 on September 30, 2028 — 691 days from this build. Upstream also publishes an extended-support phase for 2 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Oracle GraalVM end of life mean for your organization?

When a version of Oracle GraalVM 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Oracle GraalVM 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.

Your options when Oracle GraalVM reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Oracle GraalVM version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Oracle GraalVM Support Options

Oracle GraalVM has 5 versions past end of life — standard security patches have stopped; 1 of them is still covered by Extended support, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Oracle GraalVM is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Oracle GraalVM?
The next Oracle GraalVM version reaching EOL is 21 on September 30, 2028. See the full table above for all version EOL dates.
When is the Oracle GraalVM support end date?
The next Oracle GraalVM support end date is September 30, 2028, when version 21 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Oracle GraalVM?
The latest active version of Oracle GraalVM is 25.3.4.1. Always verify against the table above as support windows can change.
What happens when Oracle GraalVM reaches end of life?
When Oracle GraalVM reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of Oracle GraalVM?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Oracle GraalVM versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

confidence: 0 high, 15 medium, 0 low (each version page shows where every date comes from) · provenance · Upstream dataset: endoflife.date API · endoflife.date · Generated at build time · How we source data →
Oracle GraalVM end-of-life status badge