CVE-2026-39852
Path Normalization Bypass in Quarkus Framework
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| quarkus | quarkus | to 3.20.6.1|end_excluding=3.27.3.1|end_excluding=3.33.1.1|end_excluding=3.35.1.1|end_excluding=3.34.7|end_excluding=3.35.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Quarkus Java framework 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. It is caused by a path normalization inconsistency between the security layer and the routing layer.
Specifically, the security layer performs authorization checks on the raw URL path, which includes matrix parameters (semicolons), while the routing layer strips these matrix parameters before matching endpoints.
An attacker can exploit this by appending a semicolon and arbitrary text to a request URL (for example, /api/admin;anything). This allows them to bypass HTTP path-based authorization policies protecting endpoints like /api/admin, while still routing to the protected endpoint.
This means unauthorized or lower-privileged users can access restricted resources by manipulating the URL path.
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated or lower-privileged users to bypass authorization controls and access protected endpoints within a Quarkus-based application.
As a result, sensitive data or administrative functions that should be restricted could be exposed to unauthorized users.
This can lead to unauthorized data access, potential data leakage, and compromise of application integrity and security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Quarkus to one of the fixed versions: 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, or 3.35.2.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized or lower-privileged users to bypass HTTP path-based authorization policies, potentially granting access to protected endpoints without proper authorization.
Such unauthorized access could lead to exposure or manipulation of sensitive data, which may impact compliance with standards and regulations like GDPR and HIPAA that require strict access controls and protection of personal or health information.
However, the provided information does not explicitly discuss compliance implications or specific regulatory impacts.