Quarkus End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Quarkus 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 | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 0 | 0.28.1 | Dec 12, 2018 | Nov 25, 2019 | — | 2449 days past EOL | EOL |
| 1 | 1.13.7 | Nov 25, 2019 | Jun 23, 2021 | Nov 20, 2021 Extended support (ended) |
1873 days past EOL | EOL |
| 2.0 | 2.0.3 | Jun 30, 2021 | Jul 22, 2021 | — | 1844 days past EOL | EOL |
| 2.1 | 2.1.4 | Jul 29, 2021 | Aug 26, 2021 | — | 1809 days past EOL | EOL |
| 2.2 | 2.2.5 | Aug 31, 2021 | Dec 21, 2021 | Jul 18, 2022 Extended support (ended) |
1692 days past EOL | EOL |
| 2.3 | 2.3.1 | Oct 6, 2021 | Oct 20, 2021 | — | 1754 days past EOL | EOL |
| 2.4 | 2.4.2 | Oct 27, 2021 | Nov 17, 2021 | — | 1726 days past EOL | EOL |
| 2.5 | 2.5.4 | Nov 24, 2021 | Dec 17, 2021 | — | 1696 days past EOL | EOL |
| 2.6 | 2.6.3 | Dec 22, 2021 | Jan 26, 2022 | — | 1656 days past EOL | EOL |
| 2.7 | 2.7.7 | Feb 2, 2022 | May 30, 2022 | Jun 14, 2023 Extended support (ended) |
1532 days past EOL | EOL |
| 2.8 | 2.8.3 | Apr 12, 2022 | May 6, 2022 | — | 1556 days past EOL | EOL |
| 2.9 | 2.9.2 | May 11, 2022 | Jun 15, 2022 | — | 1516 days past EOL | EOL |
| 2.10 | 2.10.4 | Jun 22, 2022 | Jul 26, 2022 | — | 1475 days past EOL | EOL |
| 2.11 | 2.11.3 | Jul 27, 2022 | Aug 24, 2022 | — | 1446 days past EOL | EOL |
| 2.12 | 2.12.3 | Aug 31, 2022 | Sep 21, 2022 | — | 1418 days past EOL | EOL |
| 2.13 | 2.13.9 | Sep 28, 2022 | Nov 7, 2022 | Apr 30, 2024 Extended support (ended) |
1371 days past EOL | EOL |
| 2.14 | 2.14.3 | Nov 9, 2022 | Dec 14, 2022 | — | 1334 days past EOL | EOL |
| 2.15 | 2.15.3 | Dec 14, 2022 | Jan 25, 2023 | — | 1292 days past EOL | EOL |
| 2.16 | 2.16.12 | Jan 25, 2023 | Oct 31, 2023 | — | 1013 days past EOL | EOL |
| 3.0 | 3.0.4 | Apr 26, 2023 | May 31, 2023 | — | 1166 days past EOL | EOL |
| 3.1 | 3.1.3 | May 31, 2023 | Jul 5, 2023 | — | 1131 days past EOL | EOL |
| 3.2 LTS | 3.2.12 | Jul 5, 2023 | Jul 5, 2024 | Aug 28, 2024 Extended support (ended) |
765 days past EOL | EOL |
| 3.3 | 3.3.3 | Aug 23, 2023 | Sep 20, 2023 | — | 1054 days past EOL | EOL |
| 3.4 | 3.4.3 | Sep 20, 2023 | Oct 25, 2023 | — | 1019 days past EOL | EOL |
| 3.5 | 3.5.3 | Oct 25, 2023 | Nov 29, 2023 | — | 984 days past EOL | EOL |
| 3.6 | 3.6.9 | Nov 29, 2023 | Jan 31, 2024 | — | 921 days past EOL | EOL |
| 3.7 | 3.7.4 | Jan 31, 2024 | Feb 28, 2024 | — | 893 days past EOL | EOL |
| 3.8 LTS | 3.8.6.1 | Feb 28, 2024 | Feb 28, 2025 | Mar 25, 2025 Extended support (ended) |
527 days past EOL | EOL |
| 3.9 | 3.9.5 | Mar 27, 2024 | Apr 30, 2024 | — | 831 days past EOL | EOL |
| 3.10 | 3.10.2 | Apr 30, 2024 | May 29, 2024 | — | 802 days past EOL | EOL |
| 3.11 | 3.11.3 | May 29, 2024 | Jun 26, 2024 | — | 774 days past EOL | EOL |
| 3.12 | 3.12.3 | Jun 26, 2024 | Jul 31, 2024 | — | 739 days past EOL | EOL |
| 3.13 | 3.13.3 | Jul 31, 2024 | Aug 28, 2024 | — | 711 days past EOL | EOL |
| 3.14 | 3.14.4 | Aug 28, 2024 | Sep 25, 2024 | — | 683 days past EOL | EOL |
| 3.15 LTS | 3.15.7 | Sep 25, 2024 | Sep 25, 2025 | Sep 26, 2025 Extended support (ended) |
318 days past EOL | EOL |
| 3.16 | 3.16.4 | Oct 30, 2024 | Nov 27, 2024 | — | 620 days past EOL | EOL |
| 3.17 | 3.17.8 | Nov 27, 2024 | Jan 29, 2025 | — | 557 days past EOL | EOL |
| 3.18 | 3.18.4 | Jan 29, 2025 | Feb 26, 2025 | — | 529 days past EOL | EOL |
| 3.19 | 3.19.4 | Feb 26, 2025 | Mar 28, 2025 | — | 499 days past EOL | EOL |
| 3.20 LTS | 3.20.6.2 | Mar 26, 2025 | Mar 28, 2026 | Mar 29, 2026 Extended support (ended) |
134 days past EOL | EOL |
| 3.21 | 3.21.4 | Mar 26, 2025 | Apr 30, 2025 | — | 466 days past EOL | EOL |
| 3.22 | 3.22.3 | Apr 30, 2025 | May 28, 2025 | — | 438 days past EOL | EOL |
| 3.23 | 3.23.4 | May 28, 2025 | Jun 25, 2025 | — | 410 days past EOL | EOL |
| 3.24 | 3.24.5 | Jun 25, 2025 | Jul 30, 2025 | — | 375 days past EOL | EOL |
| 3.25 | 3.25.4 | Jul 30, 2025 | Aug 28, 2025 | — | 346 days past EOL | EOL |
| 3.26 | 3.26.4 | Aug 28, 2025 | Sep 24, 2025 | — | 319 days past EOL | EOL |
| 3.27 LTS | 3.27.5.1 | Sep 24, 2025 | Sep 24, 2026 | — | 46 days remaining | Warning |
| 3.28 | 3.28.5 | Sep 24, 2025 | Oct 29, 2025 | — | 284 days past EOL | EOL |
| 3.29 | 3.29.4 | Oct 29, 2025 | Nov 26, 2025 | — | 256 days past EOL | EOL |
| 3.30 | 3.30.8 | Nov 26, 2025 | Jan 28, 2026 | — | 193 days past EOL | EOL |
| 3.31 | 3.31.4 | Jan 28, 2026 | Feb 26, 2026 | — | 164 days past EOL | EOL |
| 3.32 | 3.32.4 | Feb 26, 2026 | Mar 25, 2026 | — | 137 days past EOL | EOL |
| 3.33 LTS | 3.33.3.1 | Mar 25, 2026 | Mar 25, 2027 | — | 228 days remaining | Active |
| 3.34 | 3.34.7 | Mar 25, 2026 | May 1, 2026 | — | 100 days past EOL | EOL |
| 3.35 | 3.35.4 | May 1, 2026 | May 27, 2026 | — | 74 days past EOL | EOL |
| 3.36 | 3.36.3 | May 27, 2026 | Jun 24, 2026 | — | 46 days past EOL | EOL |
| 3.37 | 3.37.4 | Jun 24, 2026 | Jul 29, 2026 | — | 11 days past EOL | EOL |
| 3.38 | 3.38.1 | Jul 29, 2026 | TBD | — | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/quarkus-framework)
What does Quarkus end of life mean for your organization?
When a version of Quarkus 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 Quarkus 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 Quarkus 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Quarkus versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Quarkus has 55 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Quarkus exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans Quarkus 2.x, 3.x. Tell us where to reach you and we'll reply with matched options and pricing guidance.