CVE-2026-39852

Modified Modified - Updated After Analysis

Path Normalization Bypass in Quarkus Framework

Publication date: 2026-05-05

Last updated on: 2026-07-03

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-05

Last Modified

2026-07-03

Generated

2026-07-06

AI Q&A

2026-05-06

EPSS Evaluated

2026-07-05

NVD

CVE-2026-39852

Affected Vendors & Products

Vendor	Product	Version / Range
quarkus	quarkus	to 3.20.6.1 (exc)
quarkus	quarkus	From 3.21.0 (inc) to 3.27.3.1 (exc)
quarkus	quarkus	From 3.28.0 (inc) to 3.33.1.1 (exc)
quarkus	quarkus	From 3.34.0 (inc) to 3.34.7 (exc)
quarkus	quarkus	From 3.35.0 (inc) to 3.35.2 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-551	If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.
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

Compliance Impact

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.

Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

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.

Hi! I’m here to help you understand CVE-2026-39852. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70