CyberSecBulletin
CVE-2026-39852NVD status: Modified

quarkus: Incorrect Authorization

Published Updated By the CyberSecBulletin desk

CVE-2026-39852 is a high-severity incorrect authorization vulnerability in quarkus from Quarkusio, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected quarkus versions: < 3.20.6.1; >= 3.27.3.0, < 3.27.3.1; >= 3.34.0, < 3.34.7, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.71% chance of exploitation within 30 days, higher than 54% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of quarkus you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Quarkusioquarkus< 3.20.6.1; >= 3.27.3.0, < 3.27.3.1; >= 3.34.0, < 3.34.7; >= 3.35.0, < 3.35.2Not stated
Red HatCryostat 4 on RHEL 9Not specified in the recordNot stated
Red HatHawtIO HawtIO 4.4.0Not specified in the recordNot stated
Red HatRed Hat Build of Apache Camel 4.14 for Quarkus 3.27Not specified in the recordNot stated
Red HatRed Hat build of Quarkus 3.20.6.SP1Not specified in the recordNot stated
Red HatRed Hat build of Quarkus 3.27.3.SP1Not specified in the recordNot stated
Red HatStreams for Apache Kafka 2.9.4Not specified in the recordNot stated
Red HatStreams for Apache Kafka 3.2.1Not specified in the recordNot stated
Red HatOpenShift ServerlessNot specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4 for Quarkus 3Not specified in the recordNot stated
Red HatRed Hat build of Apicurio Registry 2Not specified in the recordNot stated
Red HatRed Hat build of Apicurio Registry 3Not specified in the recordNot stated
Red HatRed Hat build of Debezium 3Not specified in the recordNot stated
Red HatRed Hat Build of KeycloakNot specified in the recordNot stated
Red HatRed Hat build of OptaPlanner 8Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat OpenShift AI (RHOAI)Not specified in the recordNot stated
Red HatRed Hat Process Automation 7Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
LowLimited modification of data is possible.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.08.8HighCNA (github.com)
CVSS 3.18.2HighNVD
CVSS 3.18.2HighCNA

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

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.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in quarkus

All quarkus vulnerabilities

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.