Quarkus · Lifecycle Status
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.
📅 Get reminded before Quarkus 3.27 reaches EOL on September 24, 2026 — alerts 90, 30 & 7 days out.
Latest Active
3.36.3
3.36 series
Next EOL
3.27
Sep 24, 2026
Active Versions
2
of 56 total
EOL Versions
53
no longer patched
Medium Risk
EOL Risk Score™ How is this calculated? →
EOL Recency
25/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 →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0 | 0.28.1 | Dec 12, 2018 | Nov 25, 2019 | 2402 days past EOL | EOL |
| 1 | 1.13.7 | Nov 25, 2019 | Jun 23, 2021 | 1826 days past EOL | EOL |
| 2.0 | 2.0.3 | Jun 30, 2021 | Jul 22, 2021 | 1797 days past EOL | EOL |
| 2.1 | 2.1.4 | Jul 29, 2021 | Aug 26, 2021 | 1762 days past EOL | EOL |
| 2.2 | 2.2.5 | Aug 31, 2021 | Dec 21, 2021 | 1645 days past EOL | EOL |
| 2.3 | 2.3.1 | Oct 6, 2021 | Oct 20, 2021 | 1707 days past EOL | EOL |
| 2.4 | 2.4.2 | Oct 27, 2021 | Nov 17, 2021 | 1679 days past EOL | EOL |
| 2.5 | 2.5.4 | Nov 24, 2021 | Dec 17, 2021 | 1649 days past EOL | EOL |
| 2.6 | 2.6.3 | Dec 22, 2021 | Jan 26, 2022 | 1609 days past EOL | EOL |
| 2.7 | 2.7.7 | Feb 2, 2022 | May 30, 2022 | 1485 days past EOL | EOL |
| 2.8 | 2.8.3 | Apr 12, 2022 | May 6, 2022 | 1509 days past EOL | EOL |
| 2.9 | 2.9.2 | May 11, 2022 | Jun 15, 2022 | 1469 days past EOL | EOL |
| 2.10 | 2.10.4 | Jun 22, 2022 | Jul 26, 2022 | 1428 days past EOL | EOL |
| 2.11 | 2.11.3 | Jul 27, 2022 | Aug 24, 2022 | 1399 days past EOL | EOL |
| 2.12 | 2.12.3 | Aug 31, 2022 | Sep 21, 2022 | 1371 days past EOL | EOL |
| 2.13 | 2.13.9 | Sep 28, 2022 | Nov 7, 2022 | 1324 days past EOL | EOL |
| 2.14 | 2.14.3 | Nov 9, 2022 | Dec 14, 2022 | 1287 days past EOL | EOL |
| 2.15 | 2.15.3 | Dec 14, 2022 | Jan 25, 2023 | 1245 days past EOL | EOL |
| 2.16 | 2.16.12 | Jan 25, 2023 | Oct 31, 2023 | 966 days past EOL | EOL |
| 3.0 | 3.0.4 | Apr 26, 2023 | May 31, 2023 | 1119 days past EOL | EOL |
| 3.1 | 3.1.3 | May 31, 2023 | Jul 5, 2023 | 1084 days past EOL | EOL |
| 3.2 LTS | 3.2.12 | Jul 5, 2023 | Jul 5, 2024 | 718 days past EOL | EOL |
| 3.3 | 3.3.3 | Aug 23, 2023 | Sep 20, 2023 | 1007 days past EOL | EOL |
| 3.4 | 3.4.3 | Sep 20, 2023 | Oct 25, 2023 | 972 days past EOL | EOL |
| 3.5 | 3.5.3 | Oct 25, 2023 | Nov 29, 2023 | 937 days past EOL | EOL |
| 3.6 | 3.6.9 | Nov 29, 2023 | Jan 31, 2024 | 874 days past EOL | EOL |
| 3.7 | 3.7.4 | Jan 31, 2024 | Feb 28, 2024 | 846 days past EOL | EOL |
| 3.8 LTS | 3.8.6.1 | Feb 28, 2024 | Feb 28, 2025 | 480 days past EOL | EOL |
| 3.9 | 3.9.5 | Mar 27, 2024 | Apr 30, 2024 | 784 days past EOL | EOL |
| 3.10 | 3.10.2 | Apr 30, 2024 | May 29, 2024 | 755 days past EOL | EOL |
| 3.11 | 3.11.3 | May 29, 2024 | Jun 26, 2024 | 727 days past EOL | EOL |
| 3.12 | 3.12.3 | Jun 26, 2024 | Jul 31, 2024 | 692 days past EOL | EOL |
| 3.13 | 3.13.3 | Jul 31, 2024 | Aug 28, 2024 | 664 days past EOL | EOL |
| 3.14 | 3.14.4 | Aug 28, 2024 | Sep 25, 2024 | 636 days past EOL | EOL |
| 3.15 LTS | 3.15.7 | Sep 25, 2024 | Sep 25, 2025 | 271 days past EOL | EOL |
| 3.16 | 3.16.4 | Oct 30, 2024 | Nov 27, 2024 | 573 days past EOL | EOL |
| 3.17 | 3.17.8 | Nov 27, 2024 | Jan 29, 2025 | 510 days past EOL | EOL |
| 3.18 | 3.18.4 | Jan 29, 2025 | Feb 26, 2025 | 482 days past EOL | EOL |
| 3.19 | 3.19.4 | Feb 26, 2025 | Mar 28, 2025 | 452 days past EOL | EOL |
| 3.20 LTS | 3.20.6.2 | Mar 26, 2025 | Mar 28, 2026 | 87 days past EOL | EOL |
| 3.21 | 3.21.4 | Mar 26, 2025 | Apr 30, 2025 | 419 days past EOL | EOL |
| 3.22 | 3.22.3 | Apr 30, 2025 | May 28, 2025 | 391 days past EOL | EOL |
| 3.23 | 3.23.4 | May 28, 2025 | Jun 25, 2025 | 363 days past EOL | EOL |
| 3.24 | 3.24.5 | Jun 25, 2025 | Jul 30, 2025 | 328 days past EOL | EOL |
| 3.25 | 3.25.4 | Jul 30, 2025 | Aug 28, 2025 | 299 days past EOL | EOL |
| 3.26 | 3.26.4 | Aug 28, 2025 | Sep 24, 2025 | 272 days past EOL | EOL |
| 3.27 LTS | 3.27.4.1 | Sep 24, 2025 | Sep 24, 2026 | 93 days remaining | Warning |
| 3.28 | 3.28.5 | Sep 24, 2025 | Oct 29, 2025 | 237 days past EOL | EOL |
| 3.29 | 3.29.4 | Oct 29, 2025 | Nov 26, 2025 | 209 days past EOL | EOL |
| 3.30 | 3.30.8 | Nov 26, 2025 | Jan 28, 2026 | 146 days past EOL | EOL |
| 3.31 | 3.31.4 | Jan 28, 2026 | Feb 26, 2026 | 117 days past EOL | EOL |
| 3.32 | 3.32.4 | Feb 26, 2026 | Mar 25, 2026 | 90 days past EOL | EOL |
| 3.33 LTS | 3.33.2.1 | Mar 25, 2026 | Mar 25, 2027 | 275 days remaining | Active |
| 3.34 | 3.34.7 | Mar 25, 2026 | May 1, 2026 | 53 days past EOL | EOL |
| 3.35 | 3.35.4 | May 1, 2026 | May 27, 2026 | 27 days past EOL | EOL |
| 3.36 | 3.36.3 | May 27, 2026 | TBD | Supported | Active |
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.
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.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →Frequently Asked Questions
What is the end-of-life date for Quarkus?
The next Quarkus version reaching EOL is 3.27 on September 24, 2026. See the full table above for all version EOL dates.
When is the Quarkus support end date?
The next Quarkus support end date is September 24, 2026, when version 3.27 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Quarkus?
The latest active version of Quarkus is 3.36.3. Always verify against the table above as support windows can change.
What happens when Quarkus reaches end of life?
When Quarkus reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Quarkus?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Quarkus versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.