GraphQL Java 21 · Version Status

GraphQL Java 21 End of Life Date

GraphQL Java 21 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (github.com); the source of each date is on the product page.

⚠ GraphQL Java 21 is past end of life. This version no longer receives security patches. 949 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 16, 2024
949 days past EOL
Latest Release
21.5
Standard release
Release Date
Jul 11, 2023
GraphQL Java 21 series
Where these dates come from
End of lifeApr 16, 2024Our catalog, built from the vendor pages · github.commedium · 1 source agrees
ReleaseJul 11, 2023Our catalog, built from the vendor pages · github.commedium · 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.
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.
Lifecycle detail

GraphQL Java 21 was released on July 11, 2023 and support ended on April 16, 2024 — a supported lifespan of 9 months, longer than the 6 months median for GraphQL Java releases. Its latest release on record is 21.5, published March 26, 2024 — 21 days before support ended. It has been past its end-of-life date for 2 years and 7 months. 4 newer GraphQL Java releases have shipped since.

All GraphQL Java versions GraphQL Java 22 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/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 →  ·  View score card →
Recommended upgrade path
GraphQL Java 26
Latest release: 26.2 · EOL: Supported
View full GraphQL Java timeline →
Extended Support
Extended GraphQL Java 21 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 GraphQL Java Versions
VersionLatestEOL DateStatus
→ 21 21.5 Apr 16, 2024 EOL
22 22.4 Apr 7, 2025 EOL
23 23.1 May 16, 2025 EOL
24 24.3 Nov 10, 2025 EOL
25 25.0 Apr 23, 2026 EOL
26 26.2 EOL Active

What does GraphQL Java 21 end of life mean?

When GraphQL Java 21 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 GraphQL Java 21 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to GraphQL Java 26 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does GraphQL Java 21 reach end of life?
GraphQL Java 21 reached end of life on April 16, 2024. This version is no longer receiving security patches.
Is GraphQL Java 21 still supported?
No. GraphQL Java 21 reached end of life on April 16, 2024 and is no longer receiving security patches.
What should I upgrade to from GraphQL Java 21?
The recommended upgrade from GraphQL Java 21 is GraphQL Java 26 — the latest actively supported version. Check the GraphQL Java full timeline for all supported versions.
What are the security risks of running GraphQL Java 21 past EOL?
Since GraphQL Java 21 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 GraphQL Java should migrate immediately or implement compensating controls.
Data from the vendor's own lifecycle pages (github.com) · Generated at build time · How we source data →