Quarkus 3.37 · Version Status

Quarkus 3.37 End of Life Date

Quarkus 3.37 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Quarkus 3.37 is actively supported. EOL date: TBD.
EOL Date
TBD
Supported
Latest Release
3.37.1
Standard release
Release Date
Jun 24, 2026
Quarkus 3.37 series
← Quarkus 3.36 All Quarkus versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/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 →
All Quarkus Versions
VersionLatestEOL DateStatus
0 0.28.1 Nov 25, 2019 EOL
1 1.13.7 Jun 23, 2021 EOL
2.0 2.0.3 Jul 22, 2021 EOL
2.1 2.1.4 Aug 26, 2021 EOL
2.2 2.2.5 Dec 21, 2021 EOL
2.3 2.3.1 Oct 20, 2021 EOL
2.4 2.4.2 Nov 17, 2021 EOL
2.5 2.5.4 Dec 17, 2021 EOL

What does Quarkus 3.37 end of life mean?

When Quarkus 3.37 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 Quarkus 3.37 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Quarkus 3.37 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Quarkus 3.37 reach end of life?
Quarkus 3.37 has already reached end of life.
Is Quarkus 3.37 still supported?
Yes, Quarkus 3.37 is currently supported. The EOL date is TBD.
What should I upgrade to from Quarkus 3.37?
The recommended upgrade from Quarkus 3.37 is Quarkus 3.37 — the latest actively supported version. Check the Quarkus full timeline for all supported versions.
What are the security risks of running Quarkus 3.37 past EOL?
When Quarkus 3.37 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 Quarkus should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →