QUARKUS COVERAGE

Quarkus 3.27 and 3.20 have ended. Your patching does not have to.

Quarkus 3.27 LTS reached the end of community maintenance on 24 September 2026, and 3.20 LTS on 28 March 2026. Quarkus 3.33 LTS follows on 25 March 2027, because each LTS line gets 12 months and a new one starts about every six months. OSSeva patches Quarkus 3.27 and 3.20 after end of life, with Critical fixes within 48 hours.

Who it is forTeams running a Quarkus 3.x LTS line that the community no longer maintains, in services that cannot take the next LTS yet
What you getSigned patched builds on the LTS line you run, with extensions and configuration unchanged. Assure adds an extension inventory and an LTS upgrade plan.
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your Quarkus line and extensions, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

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

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Quarkus LTS lines and community maintenance dates, read on 19 November 2026

Dates and latest releases are from quarkus.io/releases, the Quarkus project's own page, and endoflife.date agrees on every end date. Non-LTS lines between them get about a month of maintenance each.

LTS lineReleasedCommunity maintenance endsLatest release on quarkus.io
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 as upcoming with a planned release on 25 November 2026.

Quarkus releases and support status →Quarkus security policy →Quarkus LTS announcement →Quarkus end-of-life chart, every line →

How the Quarkus LTS calendar works against an upgrade plan

Quarkus support is a rolling calendar rather than a single end date, which changes how a team should plan. The points below are from the project's own pages.

  • Two LTS lines are maintained at once. Each LTS gets 12 months and a new one arrives about every six months, so today 3.33 (to 25 March 2027) and 3.40 (to 30 September 2027) overlap by six months.
  • Non-LTS lines are short. 3.39 was maintained from 26 August to 30 September 2026. Pinning a non-LTS line leaves about a month, and quarkus.io recommends the latest LTS release for production.
  • Fixes ship as micro releases, some with a fourth number. 3.27.6.1, 3.33.4.2 and 3.40.1.2 are the newest on quarkus.io. A patch applied to the line you run should keep that numbering rather than force a minor upgrade.
  • Commercial build windows differ from the community's. quarkus.io lists the Red Hat build of Quarkus 3.27 until 1 December 2026 and 3.33 until 10 May 2027, and the IBM Enterprise Build 3.27 until 26 November 2026 and 3.33 until 29 May 2027, each followed by open-ended IBM support. A team on a Red Hat or IBM build has its own date, separate from the community one.
  • The security policy supports the latest 3.x and the supported LTS lines, and its table lists 3.33 LTS. Older 3.x lines are marked unsupported, so a scanner policy that requires a supported version will flag 3.27 and 3.20.
  • Check the extensions as well as the core. The policy says reports can concern Quarkus extensions, Quarkiverse extensions and SmallRye projects, and the recent GitHub advisories name individual extensions such as the HTTP, REST Data Panache, Qute and OIDC modules. Know which of those your service loads.

Sources: quarkus.io/releases, /security, /support and /blog/lts-releases, the quarkusio/quarkus GitHub advisories (GHSA-3m97-hv84-whgc names 3.27.6.1, 3.33.4.1 and 3.40.2 as fixed versions) and endoflife.date, read on 19 November 2026. The CVE records for these advisories are filed by Red Hat and do not give the community ranges, so no CVE ids are listed.

Hibernate ORM support →Spring Boot support →Java versions and end dates →Quarkus GitHub security advisories →

Why now

A Quarkus LTS line lasts 12 months

Quarkus introduced LTS releases on 6 July 2023 with 12 months of support and a new LTS about every six months. Community maintenance for 3.20 ended on 28 March 2026 and for 3.27 on 24 September 2026. 3.33 ends on 25 March 2027, and 3.40, released on 30 September 2026, runs to 30 September 2027.

Older lines get fixes without a commitment

The Quarkus security policy commits fixes to the latest 3.x and the supported LTS and says it may fix older lines depending on severity. quarkus.io lists 3.27.6.1 on 19 October 2026, after the line's stated end, and a GitHub advisory of 16 November 2026 names it as a fixed version. Nothing guarantees the next one.

Quarkus 4.0 is scheduled for 25 November 2026

quarkus.io/releases lists Quarkus 4.0 as upcoming, with a planned release on 25 November 2026, and recent GitHub advisories already name 4.0.0 beta builds. A team on 3.20 or 3.27 faces two steps: catching up to the 3.40 LTS, then deciding on 4.0.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
3.20 LTS(Community EOL 28 Mar 2026)EOLSee advisories
3.27 LTS(Community EOL 24 Sep 2026)EOLSee advisories
3.33 LTS(Community maintenance to 25 Mar 2027. Assessed case by case.)CurrentSee advisories
3.40 LTS(Community maintenance to 30 Sep 2027. Assessed case by case.)CurrentSee advisories
Quarkus end of life dates for every version →

Running a Quarkus version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for Quarkus 3.27 and 3.20 LTS after end of community maintenance.

  • Backported security fixes for Quarkus 3.27 and 3.20 LTS
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and a Quarkus upgrade plan.

  • Everything in Patch
  • Extension inventory: core, Quarkiverse and SmallRye extensions in use
  • LTS-to-LTS upgrade path assessment toward 3.40
  • SOC 2 / HIPAA attestation package
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application and runtime monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Is Quarkus 3.27 end of life?

Community maintenance for Quarkus 3.27 LTS ended on 24 September 2026, per quarkus.io/releases, and endoflife.date agrees. quarkus.io still lists 3.27.6.1, released on 19 October 2026, so a fix can appear after the date, but the security policy only commits to the supported lines.

Which Quarkus versions does OSSeva patch?

The Quarkus 3.27 and 3.20 LTS lines after community maintenance. Other lines are assessed case by case through a version coverage check.

When does Quarkus 3.33 reach end of life?

Community maintenance for Quarkus 3.33 LTS ends on 25 March 2027, per quarkus.io/releases. quarkus.io lists the Red Hat build of Quarkus 3.33 until 10 May 2027.

Which Quarkus version is the current LTS?

Quarkus 3.40, released on 30 September 2026, with community maintenance until 30 September 2027, per quarkus.io/releases, which recommends the latest LTS for production.

Does the Quarkus security policy cover older versions?

It commits to the latest major.minor and the supported LTS lines and says older lines may be fixed depending on severity and age. For an end-of-life version, the policy says a real vulnerability still gets a CVE, tagged unsupported-when-assigned if no supported version is affected.

Does Quarkus support extensions outside the core project?

Security reports to Quarkus can concern the Quarkus extension, a Quarkiverse extension or a SmallRye project, per the security policy. OSSeva's Assure tier inventories which of them your services use, because a Quarkus patch is only as complete as the extension set it covers.

How fast are Quarkus vulnerabilities patched?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.

How is OSSeva Quarkus support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get Quarkus patched and supported?

Tell us your Quarkus versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

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

Prefer to talk or read more first?

Book a call