Quarkus Framework 3.25 · Version Status

Quarkus Framework 3.25 End of Life Date

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

Quarkus Framework 3.25 is past end of life. This version no longer receives security patches. 254 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 28, 2025
254 days past EOL
Latest Release
3.25.4
Standard release
Release Date
Jul 30, 2025
Quarkus Framework 3.25 series
← Quarkus Framework 3.24 All Quarkus Framework versions Quarkus Framework 3.26 →
Recommended upgrade path
Quarkus Framework 3.33
Latest release: 3.33.1.1 · EOL: Mar 25, 2027
View full Quarkus Framework timeline →
All Quarkus Framework 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 Framework 3.25 end of life mean?

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

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

Frequently Asked Questions
When does Quarkus Framework 3.25 reach end of life?
Quarkus Framework 3.25 reached end of life on August 28, 2025. This version is no longer receiving security patches.
Is Quarkus Framework 3.25 still supported?
No. Quarkus Framework 3.25 reached end of life on August 28, 2025 and is no longer receiving security patches.
What should I upgrade to from Quarkus Framework 3.25?
The recommended upgrade from Quarkus Framework 3.25 is Quarkus Framework 3.33 — the latest actively supported version. Check the Quarkus Framework full timeline for all supported versions.
What are the security risks of running Quarkus Framework 3.25 past EOL?
When Quarkus Framework 3.25 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 Framework should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →