Quarkus EOL: end-of-life dates for every Quarkus LTS line

Quarkus 3.27 LTS reached the end of community maintenance on 24 September 2026 and Quarkus 3.20 LTS on 28 March 2026. Quarkus 3.33 LTS ends on 25 March 2027 and 3.40 LTS, the current one, on 30 September 2027. Each LTS line gets 12 months. Dates checked against quarkus.io and endoflife.date on 19 November 2026.

Only your email is required · An engineer replies within 1 business day · No commitment

Latest release
3.40.1.2
Supported lines
2
End-of-life lines
58
Next end of life
3.33 · 25 Mar 2027

Quarkus 3.27 and 3.20 have ended

Move to the next LTS, or keep 3.27 and 3.20 patched

Most services should move to the current LTS. When an extension, a certification or a release freeze holds a service on 3.27 or 3.20, OSSeva patches both. Other Quarkus lines are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.

Quarkus release timeline

SupportRHBQTodayChart shows the 14 newest lines; the table lists all.

All Quarkus versions, release dates and end-of-life dates

VersionReleasedSupportRHBQLatestOSSeva
3.40 (LTS)2 months ago(30 Sept 2026)Ends in 10 months(30 Sept 2027)Ends in 10 months(30 Sept 2027)3.40.1.2–
3.393 months ago(27 Aug 2026)Ended 2 months ago(30 Sept 2026)Ended3.39.5–
3.384 months ago(29 Jul 2026)Ended 3 months ago(27 Aug 2026)Ended3.38.3–
3.375 months ago(24 Jun 2026)Ended 4 months ago(29 Jul 2026)Ended3.37.4–
3.366 months ago(27 May 2026)Ended 5 months ago(24 Jun 2026)Ended3.36.3–
3.357 months ago(1 May 2026)Ended 6 months ago(27 May 2026)Ended3.35.4–
3.348 months ago(25 Mar 2026)Ended 7 months ago(1 May 2026)Ended3.34.7–
3.33 (LTS)8 months ago(25 Mar 2026)Ends in 4 months(25 Mar 2027)Ends in 6 months(10 May 2027)3.33.4.2–
3.329 months ago(26 Feb 2026)Ended 8 months ago(25 Mar 2026)Ended3.32.4–
3.3110 months ago(28 Jan 2026)Ended 9 months ago(26 Feb 2026)Ended3.31.4–
3.301 year ago(26 Nov 2025)Ended 10 months ago(28 Jan 2026)Ended3.30.8–
3.291 year and 1 month ago(29 Oct 2025)Ended 1 year ago(26 Nov 2025)Ended3.29.4–
3.281 year and 2 months ago(24 Sept 2025)Ended 1 year and 1 month ago(29 Oct 2025)Ended3.28.5–
3.27 (LTS)1 year and 2 months ago(24 Sept 2025)Ended 2 months ago(24 Sept 2026)Ends in 9 days(1 Dec 2026)3.27.6.1–
3.261 year and 3 months ago(28 Aug 2025)Ended 1 year and 2 months ago(24 Sept 2025)Ended3.26.4–
3.251 year and 4 months ago(30 Jul 2025)Ended 1 year and 3 months ago(28 Aug 2025)Ended3.25.4–
3.241 year and 5 months ago(25 Jun 2025)Ended 1 year and 4 months ago(30 Jul 2025)Ended3.24.5–
3.231 year and 6 months ago(28 May 2025)Ended 1 year and 5 months ago(25 Jun 2025)Ended3.23.4–
3.221 year and 7 months ago(30 Apr 2025)Ended 1 year and 6 months ago(28 May 2025)Ended3.22.3–
3.211 year and 8 months ago(26 Mar 2025)Ended 1 year and 7 months ago(30 Apr 2025)Ended3.21.4–
3.20 (LTS)1 year and 8 months ago(26 Mar 2025)Ended 8 months ago(28 Mar 2026)Ended 7 months ago(23 Apr 2026)3.20.6.2–
3.191 year and 9 months ago(26 Feb 2025)Ended 1 year and 8 months ago(28 Mar 2025)Ended3.19.4–
3.181 year and 10 months ago(29 Jan 2025)Ended 1 year and 9 months ago(26 Feb 2025)Ended3.18.4–
3.172 years ago(27 Nov 2024)Ended 1 year and 10 months ago(29 Jan 2025)Ended3.17.8–
3.162 years and 1 month ago(30 Oct 2024)Ended 2 years ago(27 Nov 2024)Ended3.16.4–
3.15 (LTS)2 years and 2 months ago(25 Sept 2024)Ended 1 year and 2 months ago(25 Sept 2025)Ended 1 year and 1 month ago(29 Oct 2025)3.15.7–
3.142 years and 3 months ago(28 Aug 2024)Ended 2 years and 2 months ago(25 Sept 2024)Ended3.14.4–
3.132 years and 4 months ago(31 Jul 2024)Ended 2 years and 3 months ago(28 Aug 2024)Ended3.13.3–
3.122 years and 5 months ago(26 Jun 2024)Ended 2 years and 4 months ago(31 Jul 2024)Ended3.12.3–
3.112 years and 6 months ago(29 May 2024)Ended 2 years and 5 months ago(26 Jun 2024)Ended3.11.3–
3.102 years and 7 months ago(30 Apr 2024)Ended 2 years and 6 months ago(29 May 2024)Ended3.10.2–
3.92 years and 8 months ago(27 Mar 2024)Ended 2 years and 7 months ago(30 Apr 2024)Ended3.9.5–
3.8 (LTS)2 years and 9 months ago(28 Feb 2024)Ended 1 year and 9 months ago(28 Feb 2025)Ended 1 year and 8 months ago(25 Mar 2025)3.8.6.1–
3.72 years and 10 months ago(31 Jan 2024)Ended 2 years and 9 months ago(28 Feb 2024)Ended3.7.4–
3.63 years ago(29 Nov 2023)Ended 2 years and 10 months ago(31 Jan 2024)Ended3.6.9–
3.53 years and 1 month ago(25 Oct 2023)Ended 3 years ago(29 Nov 2023)Ended3.5.3–
3.43 years and 2 months ago(20 Sept 2023)Ended 3 years and 1 month ago(25 Oct 2023)Ended3.4.3–
3.33 years and 3 months ago(23 Aug 2023)Ended 3 years and 2 months ago(20 Sept 2023)Ended3.3.3–
3.2 (LTS)3 years and 5 months ago(5 Jul 2023)Ended 2 years and 5 months ago(5 Jul 2024)Ended 2 years and 3 months ago(28 Aug 2024)3.2.12–
3.13 years and 6 months ago(31 May 2023)Ended 3 years and 5 months ago(5 Jul 2023)Ended3.1.3–
3.03 years and 7 months ago(26 Apr 2023)Ended 3 years and 6 months ago(31 May 2023)Ended3.0.4–
2.163 years and 10 months ago(25 Jan 2023)Ended 3 years and 1 month ago(31 Oct 2023)Ended2.16.12–
2.153 years and 11 months ago(14 Dec 2022)Ended 3 years and 10 months ago(25 Jan 2023)Ended2.15.3–
2.144 years ago(9 Nov 2022)Ended 3 years and 11 months ago(14 Dec 2022)Ended2.14.3–
2.134 years and 2 months ago(28 Sept 2022)Ended 4 years ago(7 Nov 2022)Ended 2 years and 7 months ago(30 Apr 2024)2.13.9–
2.124 years and 3 months ago(31 Aug 2022)Ended 4 years and 2 months ago(21 Sept 2022)Ended2.12.3–
2.114 years and 4 months ago(27 Jul 2022)Ended 4 years and 3 months ago(24 Aug 2022)Ended2.11.3–
2.104 years and 5 months ago(22 Jun 2022)Ended 4 years and 4 months ago(26 Jul 2022)Ended2.10.4–
2.94 years and 6 months ago(11 May 2022)Ended 4 years and 5 months ago(15 Jun 2022)Ended2.9.2–
2.84 years and 7 months ago(12 Apr 2022)Ended 4 years and 7 months ago(6 May 2022)Ended2.8.3–
2.74 years and 10 months ago(2 Feb 2022)Ended 4 years and 6 months ago(30 May 2022)Ended 3 years and 5 months ago(14 Jun 2023)2.7.7–
2.64 years and 11 months ago(22 Dec 2021)Ended 4 years and 10 months ago(26 Jan 2022)Ended2.6.3–
2.55 years ago(24 Nov 2021)Ended 4 years and 11 months ago(17 Dec 2021)Ended2.5.4–
2.45 years and 1 month ago(27 Oct 2021)Ended 5 years ago(17 Nov 2021)Ended2.4.2–
2.35 years and 2 months ago(6 Oct 2021)Ended 5 years and 1 month ago(20 Oct 2021)Ended2.3.1–
2.25 years and 3 months ago(31 Aug 2021)Ended 4 years and 11 months ago(21 Dec 2021)Ended 4 years and 4 months ago(18 Jul 2022)2.2.5–
2.15 years and 4 months ago(29 Jul 2021)Ended 5 years and 3 months ago(26 Aug 2021)Ended2.1.4–
2.05 years and 5 months ago(30 Jun 2021)Ended 5 years and 4 months ago(22 Jul 2021)Ended2.0.3–
17 years ago(25 Nov 2019)Ended 5 years and 5 months ago(23 Jun 2021)Ended 5 years ago(20 Nov 2021)1.13.7–
07 years and 11 months ago(12 Dec 2018)Ended 7 years ago(25 Nov 2019)Ended0.28.1–

Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: quarkus.io. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.

How long does a Quarkus LTS line last?

Twelve months. Quarkus announced LTS releases on 6 July 2023, with 12 months of support and a new LTS about every six months. The first was 3.2. Because a new LTS starts every six months, two LTS lines are maintained at once and an end date arrives twice a year: 3.27 ended on 24 September 2026, and 3.33 ends on 25 March 2027.

Between LTS releases the project ships a minor release about every month, and each is maintained only until the next one. 3.39 ran from 26 August to 30 September 2026. quarkus.io recommends the latest LTS for production.

Quarkus LTS lines. Source: quarkus.io/releases, read on 19 November 2026, and endoflife.date.

LTS lineReleasedCommunity maintenance endsLatest release listed
3.4030 Sep 202630 Sep 20273.40.1.2 (9 Nov 2026)
3.3325 Mar 202625 Mar 20273.33.4.2 (9 Nov 2026)
3.2724 Sep 202524 Sep 20263.27.6.1 (19 Oct 2026)
3.2026 Mar 202528 Mar 20263.20.6.2 (17 Jun 2026)
3.1525 Sep 202425 Sep 20253.15.7 (24 Sep 2025)
2.1625 Jan 202331 Oct 20232.16.12 (17 Oct 2023)

Quarkus 4.0 is listed on quarkus.io/releases as upcoming, with a planned release on 25 November 2026.

What does Quarkus fix after an LTS line ends?

The Quarkus security policy commits security fixes to the latest major.minor version and the supported LTS lines, and says it may fix older lines depending on severity and age. A real vulnerability in an end-of-life version still gets a CVE, tagged unsupported-when-assigned when no supported version is affected.

In practice a fix can still appear after the date. quarkus.io lists 3.27.6.1 on 19 October 2026, after 3.27's stated end, and a Quarkus GitHub advisory published on 16 November 2026 names 3.27.6.1 as fixed alongside 3.33.4.1 and 3.40.2. The policy does not promise that again, so a scanner or auditor that requires a supported version will flag 3.27 and 3.20.

Who patches Quarkus after end of life?

OSSeva patches the Quarkus 3.27 and 3.20 LTS lines after community maintenance, and assesses other lines case by case. quarkus.io also lists commercial builds with their own dates: the Red Hat build of Quarkus 3.27 until 1 December 2026 and 3.33 until 10 May 2027, and the IBM Enterprise Build of Quarkus 3.27 until 26 November 2026 and 3.33 until 29 May 2027, each followed by open-ended IBM support.

Facts from quarkus.io/releases, read on 19 November 2026. We read no vendor page for this table.

OptionQuarkus 3.27Quarkus 3.33
Quarkus communityEnded 24 Sep 2026Ends 25 Mar 2027
Red Hat build of QuarkusUntil 1 Dec 2026Until 10 May 2027
IBM Enterprise Build of QuarkusUntil 26 Nov 2026, then open-ended supportUntil 29 May 2027, then open-ended support
OSSevaPatched after end of lifeAssessed case by case

How we compared: the Red Hat and IBM rows are what quarkus.io lists, not what either vendor's own page says. Confirm the terms with the vendor.

Running an end-of-life Quarkus version?

OSSeva keeps end-of-life Quarkus patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.

Quarkus extended support

Questions

Quarkus end of life: common questions

Book a 15-minute call

When is the next Quarkus end of life?

Quarkus 3.33 LTS reaches the end of community maintenance on 25 March 2027. The security policy commits fixes only to the latest major.minor and the supported LTS lines, and says it may fix older lines depending on severity and age. A fix can still appear after the date: quarkus.io lists 3.27.6.1 on 19 October 2026, after 3.27's end on 24 September 2026. A scanner or auditor that requires a supported version will still flag the ended line.

Is Quarkus 3.27 end of life?

Yes. Community maintenance for Quarkus 3.27 LTS ended on 24 September 2026, per quarkus.io/releases. The page still lists 3.27.6.1, released on 19 October 2026, but the security policy only commits to the supported lines.

When does Quarkus 3.33 reach end of life?

25 March 2027, when its 12 months of community maintenance end. 3.33 LTS was released on 25 March 2026.

Does Quarkus have LTS releases?

Yes. Quarkus announced LTS releases on 6 July 2023, starting with 3.2. An LTS line gets 12 months of support and a new one is released about every six months. The current LTS is 3.40, released on 30 September 2026.

Is Quarkus 3.20 end of life?

Yes. Community maintenance for Quarkus 3.20 LTS ended on 28 March 2026. quarkus.io lists 3.20.6.2 from 17 June 2026 as its latest release.

Which Quarkus version should I run?

quarkus.io says to use the latest LTS release for production, currently 3.40. Quarkus 4.0 is listed as upcoming with a planned release on 25 November 2026.

Is Quarkus 2.16 end of life?

Yes. Community maintenance for Quarkus 2.16 ended on 31 October 2023, and 2.16.12.Final from 17 October 2023 was its last release.

What is the latest Quarkus version?

3.40.1.2, released 9 Nov 2026, on the 3.40 (LTS) line. Other supported lines: 3.33.

Which Quarkus versions are still supported?

3.40 (until 30 Sept 2027) and 3.33 (until 25 Mar 2027). Every other line has reached end of life, per the dates in the table above.

Can I get security patches for an end-of-life Quarkus version?

Yes. OSSeva provides Quarkus extended support after upstream support ends, on the Patch, Assure and Operate tiers. See Quarkus extended support for the versions covered.

Get a quote

Still running an end-of-life Quarkus?

Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call