Quarkus 3.27.6 is planned as the last update in its LTS line

Quarkus 3.27.6 is planned as the last update in the 3.27 long-term-support stream, turning an otherwise routine maintenance release into a lifecycle decision for application teams. The release announcement tells users still on 3.27 to begin moving to Quarkus 3.33 or 3.40, which it identifies as the next LTS.

What changed

The Quarkus project says 3.27.6 contains bug fixes, documentation updates and security fixes, and describes it as a safe upgrade for applications already on the 3.27 stream.

The security rollup is broad rather than centered on one project-rated critical event. The release lists fixes across Quarkus and direct dependencies, including denial-of-service issues in Jackson, SmallRye Fault Tolerance, OpenNLP, LZ4 Java and RESTEasy; a path-traversal issue in FreeMarker; a Qute cross-site-scripting flaw; and multiple MariaDB Connector/J problems involving local-file controls, credential handling and character-set changes. The project’s announcement does not characterize any of those issues as known exploited in the wild.

Why the lifecycle note matters

The important sentence is the one about what comes next: 3.27.6 is the final update currently planned for the 3.27 line. That changes the operational question from whether to take one maintenance patch to which supported stream a team should standardize on next.

Teams that remain on 3.27 should still apply 3.27.6, because it is the release carrying the accumulated fixes. But they should treat that deployment as a bridge rather than a stable endpoint. The project explicitly points to 3.33 or 3.40; platform owners will need to choose based on their extension compatibility, test coverage and the timing of their next application release.

What teams should do

The project recommends using the current Quarkus CLI and running quarkus update --stream=3.27 to move applications on that stream to 3.27.6.

Beyond that sourced recommendation, this desk’s analysis is that teams should open a separate migration track for 3.33 or 3.40 rather than allowing the maintenance update to close the work item. That work should include extension compatibility checks, application regression tests and review of dependency overrides that could mask versions delivered by the platform.

The lifecycle decision should remain distinct from the CVE list. The patch is worth taking now, but the lasting consequence of 3.27.6 is that the project has no further 3.27 maintenance release planned.