Quarkus authorization bypass via semicolon path normalization inconsistency

Summary

Quarkus is a Java framework for building cloud-native applications. In versions prior to 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, and 3.35.2, a path normalization inconsistency between the security layer and the routing layer allows unauthenticated or lower-privileged users to bypass HTTP path-based authorization policies. Quarkus's security layer performs authorization checks on the raw URL path which preserves matrix parameters (semicolons), while RESTEasy Reactive's routing layer strips matrix parameters before matching endpoints. An attacker can append a semicolon and arbitrary text to a request URL (e.g., /api/admin;anything) to bypass policies protecting /api/admin while still routing to the protected endpoint. This issue has been fixed in versions 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, and 3.35.2.

Timeline

1. May 5, 2026, 8:58 PM UTCCVE published
2. May 6, 2026, 12:53 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Aug 17, 2026, 12:05 PM UTCRecord last updated

Affected versions

• quarkusio quarkus

  fixed in 3.20.6.1; From 3.27.3.0 · fixed in 3.27.3.1; From 3.34.0 · fixed in 3.34.7; From 3.35.0 · fixed in 3.35.2

• io.quarkus:quarkus-vertx-httpMaven

  fixed in 3.20.6.1

• io.quarkus:quarkus-vertx-httpMaven

  From 3.21.0 · fixed in 3.27.3.1

• io.quarkus:quarkus-vertx-httpMaven

  From 3.30.0 · fixed in 3.33.1.1

• io.quarkus:quarkus-vertx-httpMaven

  From 3.34.0 · fixed in 3.35.1.1

References 1