End-of-Life Releases

Guidance for applications running on unsupported Quarkus versions.

What Happens When a Release Reaches End-of-Life

When a Quarkus release reaches End-of-Life, it no longer receives security patches, bug fixes, or community support. Running EOL versions exposes your applications to unpatched vulnerabilities, ecosystem drift, and compliance risks.

No More Vulnerability Fixes

Security vulnerabilities discovered after EOL will not be patched. Your applications remain exposed to known exploits.

Ecosystem Drift

Extensions and libraries drop support for EOL versions, making it progressively harder to update dependencies.

Toolchain Breakage

Build tools, CI systems, and shared libraries may introduce incompatibilities that are never resolved for EOL releases.

Compliance Risks

Industry audits and security frameworks flag unmaintained runtimes, potentially blocking deployments and certifications.

We recommend upgrading to an LTS release. LTS releases are maintained for 12 months with critical bug fixes and security patches.

EOL Versions

Release Released End of Life Final Patch
3.35 01 May 2026 27 May 2026 3.35.4
3.34 25 Mar 2026 01 May 2026 3.34.7
3.32 26 Feb 2026 25 Mar 2026 3.32.4
3.31 28 Jan 2026 26 Feb 2026 3.31.4
3.30 26 Nov 2025 28 Jan 2026 3.30.8
3.29 29 Oct 2025 26 Nov 2025 3.29.4
3.28 24 Sep 2025 29 Oct 2025 3.28.5
3.26 28 Aug 2025 24 Sep 2025 3.26.4
3.25 30 Jul 2025 28 Aug 2025 3.25.4
3.24 25 Jun 2025 30 Jul 2025 3.24.5
3.23 28 May 2025 25 Jun 2025 3.23.4
3.22 30 Apr 2025 28 May 2025 3.22.3
3.21 26 Mar 2025 30 Apr 2025 3.21.4
3.20 LTS 26 Mar 2025 28 Mar 2026 3.20.6.2
3.19 26 Feb 2025 28 Mar 2025 3.19.4
3.18 29 Jan 2025 26 Feb 2025 3.18.4
3.17 27 Nov 2024 29 Jan 2025 3.17.8
3.16 30 Oct 2024 27 Nov 2024 3.16.4
3.15 LTS 25 Sep 2024 25 Sep 2025 3.15.7
3.14 28 Aug 2024 25 Sep 2024 3.14.4
3.13 31 Jul 2024 28 Aug 2024 3.13.3
3.12 26 Jun 2024 31 Jul 2024 3.12.3
3.11 29 May 2024 26 Jun 2024 3.11.3
3.10 30 Apr 2024 29 May 2024 3.10.2
3.9 27 Mar 2024 30 Apr 2024 3.9.5
3.8 LTS 28 Feb 2024 28 Feb 2025 3.8.6.1
3.7 31 Jan 2024 28 Feb 2024 3.7.4
3.6 29 Nov 2023 31 Jan 2024 3.6.9
3.5 25 Oct 2023 29 Nov 2023 3.5.3
3.4 20 Sep 2023 25 Oct 2023 3.4.3
3.3 23 Aug 2023 20 Sep 2023 3.3.3
3.2 LTS 05 Jul 2023 05 Jul 2024 3.2.12
3.1 31 May 2023 05 Jul 2023 3.1.3
3.0 26 Apr 2023 31 May 2023 3.0.4
2.16 25 Jan 2023 31 Oct 2023 2.16.12
2.15 14 Dec 2022 25 Jan 2023 2.15.3
2.14 09 Nov 2022 14 Dec 2022 2.14.3
2.13 28 Sep 2022 07 Nov 2022 2.13.9
2.12 31 Aug 2022 21 Sep 2022 2.12.3
2.11 27 Jul 2022 24 Aug 2022 2.11.3
2.10 22 Jun 2022 26 Jul 2022 2.10.4
2.9 11 May 2022 15 Jun 2022 2.9.2
2.8 12 Apr 2022 06 May 2022 2.8.3
2.7 02 Feb 2022 30 May 2022 2.7.7
2.6 22 Dec 2021 26 Jan 2022 2.6.3
2.5 24 Nov 2021 17 Dec 2021 2.5.4
2.4 27 Oct 2021 17 Nov 2021 2.4.2
2.3 06 Oct 2021 20 Oct 2021 2.3.1
2.2 31 Aug 2021 21 Dec 2021 2.2.5
2.1 29 Jul 2021 26 Aug 2021 2.1.4
2.0 30 Jun 2021 22 Jul 2021 2.0.3
1 25 Nov 2019 23 Jun 2021 1.13.7
0 12 Dec 2018 25 Nov 2019 0.28.1

Enterprise Support

Enterprise offerings of Quarkus are actively maintained with longer lifecycles than the community releases. Some versions listed in the table above may still be under active enterprise support. See the releases page for details.

On-Demand Patches for EOL Versions

If your organisation is not yet ready to upgrade from an EOL version, the following vendors can provide security patches and fixes on request.

IBM Enterprise Build of Quarkus

IBM may provide on-demand patches for older versions of their enterprise Quarkus products, even after the community release has reached end-of-life.

HeroDevs Never-Ending Support

HeroDevs provides on-demand security patches and compliance support for EOL Quarkus versions, bridging the gap while you plan your upgrade.