Mandrel 24.0 (JDK 22) · Version Status

Mandrel 24.0 (JDK 22) End of Life Date

Mandrel 24.0 (JDK 22) 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.

Mandrel 24.0 (JDK 22) is past end of life. This version no longer receives security patches. 697 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 15, 2024
697 days past EOL
Latest Release
24.0.2.0
Standard release
Release Date
Mar 27, 2024
Mandrel 24.0 (JDK 22) series
Lifecycle detail

Mandrel 24.0 was released on March 27, 2024 and support ended on October 15, 2024 — a supported lifespan of 7 months, in line with the 7 months median for Mandrel releases. It was not an LTS release; Mandrel reserves longer patch windows for its LTS versions. The last patch it will ever receive is 24.0.2.0, published July 21, 2024 — 3 months before support ended. It has been without security patches for 1 year and 11 months. 2 newer Mandrel releases have shipped since.

← Mandrel 23.1 (JDK 21) All Mandrel versions Mandrel 24.1 (JDK 23) →
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/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
Mandrel 25.0 (JDK 25)
Latest release: 25.0.4.1 · EOL: Supported
View full Mandrel timeline →
Extended Support
Extended Mandrel 24.0 (JDK 22) support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Mandrel Versions
VersionLatestEOL DateStatus
20.1 (JDK 11) 20.1.0.4 Apr 20, 2021 EOL
20.2 (JDK 11) 20.2.0.0 Jan 8, 2021 EOL
20.3 (JDK 11) LTS 20.3.3.0 Oct 19, 2021 EOL
21.0 (JDK 11) 21.0.0.0 Apr 26, 2021 EOL
21.1 (JDK 11) 21.1.0.0 Jul 20, 2021 EOL
21.2 (JDK 11) LTS 21.2.0.2 Jan 18, 2022 EOL
21.3 (JDK 11, JDK 17) LTS 21.3.6.0 Jul 17, 2023 EOL
22.1 (JDK 11, JDK 17) 22.0.0.2 Apr 26, 2022 EOL

What does Mandrel 24.0 (JDK 22) end of life mean?

When Mandrel 24.0 (JDK 22) 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Mandrel 24.0 (JDK 22) past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Mandrel 25.0 (JDK 25) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Mandrel 24.0 (JDK 22) reach end of life?
Mandrel 24.0 (JDK 22) reached end of life on October 15, 2024. This version is no longer receiving security patches.
Is Mandrel 24.0 (JDK 22) still supported?
No. Mandrel 24.0 (JDK 22) reached end of life on October 15, 2024 and is no longer receiving security patches.
What should I upgrade to from Mandrel 24.0 (JDK 22)?
The recommended upgrade from Mandrel 24.0 (JDK 22) is Mandrel 25.0 (JDK 25) — the latest actively supported version. Check the Mandrel full timeline for all supported versions.
What are the security risks of running Mandrel 24.0 (JDK 22) past EOL?
When Mandrel 24.0 (JDK 22) reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Mandrel should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →