GraphQL Java End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all GraphQL Java versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 21 | 21.5 | Jul 11, 2023 | Apr 16, 2024 | 858 days past EOL | EOL |
| 22 | 22.4 | Apr 16, 2024 | Apr 7, 2025 | 502 days past EOL | EOL |
| 23 | 23.1 | Apr 7, 2025 | May 16, 2025 | 463 days past EOL | EOL |
| 24 | 24.3 | May 16, 2025 | Nov 10, 2025 | 285 days past EOL | EOL |
| 25 | 25.0 | Nov 10, 2025 | Apr 23, 2026 | 121 days past EOL | EOL |
| 26 | 26.0 | Apr 23, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/graphql-java)
GraphQL Java lifecycle status — the real story
graphql-java is the engine under most JVM GraphQL deployments, including Spring for GraphQL and Netflix DGS. Its lifecycle profile is defined by a fast major-release cadence — roughly two majors per year (21 in 2023, 22 and 23/24 through 2024-25, 26 by April 2026) — combined with a latest-version support posture, meaning each major is effectively end-of-life within months of its successor.
In practice enterprises pin graphql-java majors for long periods because upgrades ripple through framework versions (each Spring for GraphQL / DGS release binds to a specific graphql-java major). That structural lag means production systems routinely run majors that are several generations unsupported.
When auditing, resolve the effective graphql-java version through the framework BOM rather than the declared dependency — the framework's binding is what pins you, and framework upgrades are the real remediation path.
What does GraphQL Java end of life mean for your organization?
When a version of GraphQL Java 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 GraphQL Java 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 GraphQL Java 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.
| Option | Best when | Watch 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, extended support vendors provide continued security patches for EOL GraphQL Java versions. This is a bridge, not a permanent solution — plan your migration in parallel.
GraphQL Java has 5 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for GraphQL Java 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."