EUVD-2026-38084
GHSA-qcxp-gm7m-4j5v
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Internet-exposed Quarkus app
-
DeliveryEnumerate protected paths and static roots
-
ExploitCraft URL with %3B matrix-param or %2F/%5C encoded separators
-
ExecutionSend unauthenticated HTTP request
-
PersistBypass path-based auth policy
-
ImpactRead protected endpoint or static resource
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Target must be running an unpatched Quarkus version (any release before the 3.37.0/3.36.3/3.33.2.1/3.33.3/3.27.4.1/3.27.5/3.20.6.2 fix line) that enforces access control via Quarkus HTTP path-based authorization policies (quarkus.http.auth.permission.*) rather than method-level annotations, OR exposes protected static resources through the built-in static handler. Exploitation is limited to disclosure of resources whose protection relies solely on path matching - applications that additionally enforce authorization at the JAX-RS method layer are not bypassed, and deployments fronted by a proxy that rejects %3B/%2F/%5C in the path are also out of reach. CVSS PR:N/UI:N confirms no authentication or user interaction is required against a vulnerable default configuration. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N scores 7.5 and is internally consistent: network-reachable, no privileges, no user interaction, with confidentiality loss when protected endpoints or static assets are exposed. EPSS, SSVC, and KEV signals were not supplied in the input, and no public exploit identified at time of analysis, so real-world exploitation pressure cannot be quantified - however, the trivial payload (URL-encoded characters in a normal HTTP request) makes this highly automatable once a target is identified. The C:H/I:N/A:N profile likely overstates impact for deployments whose protected paths only enforce authorization for non-sensitive endpoints, and understates it for tenants where authorization gates business data; defenders should treat this as a high-priority patch given the explicit prior-bypass lineage with CVE-2026-39852. |
| Exploit ScenarioDerived | An unauthenticated attacker sends an HTTP request to a Quarkus application such as GET /admin%3Bfoo=bar/users or GET /public%2F..%2Fadmin/config, where the encoded semicolon or slash causes the path-based authorization policy to match a permitted prefix while the router dispatches to the protected admin endpoint or static file. Because no authentication is required and the request is a single crafted URL, the technique is trivially scriptable across Internet-exposed Quarkus services. No public exploit identified at time of analysis, though the advisory text describes the bypass primitives clearly enough to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 19, 2026
Authentication bypass in Quarkus Java framework allows remote unauthenticated attackers to circumvent HTTP path-based authorization policies by smuggling encoded semicolons (%3B) as matrix parameters or by using encoded slashes (%2F) and backslashes (%5C) to reach protected static resources. Affects all Quarkus versions prior to the 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2 patch line. No public exploit identified at time of analysis, though the issue is a documented bypass of the prior CVE-2026-39852 fix.
RemediationAI
Vendor-released patch: upgrade to Quarkus 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, or 3.20.6.2 - whichever matches your current maintenance line - per GHSA-qcxp-gm7m-4j5v (https://github.com/quarkusio/quarkus/security/advisories/GHSA-qcxp-gm7m-4j5v). Until upgrade is possible, place a reverse proxy or WAF in front of the application that rejects or normalizes requests containing %3B, %2F, and %5C in the path component before they reach Quarkus, accepting that this may break legitimate clients that send matrix parameters; alternatively, move authorization enforcement from path-based policies to method-level @RolesAllowed/@PermissionsAllowed annotations on the JAX-RS resources themselves so encoded-path tricks cannot smuggle past the security layer, at the cost of refactoring effort. Audit served static resources and remove sensitive files from any directory exposed through the Quarkus static-resource handler.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Quarkus is a Kubernetes-native Java framework (cpe:2.3:a:quarkusio:quarkus) that ships an HTTP layer with declarative path-based security policies (@PermissionsAllowed, application.properties quarkus.http.auth.permission.*). The flaw is a CWE-287 authentication bypass rooted in inconsistent URL normalization between the security interceptor and the request dispatcher: the authorization layer evaluates a normalized path while the downstream router decodes %3B, %2F, and %5C differently, so matrix-parameter segments and encoded path separators reach protected resources without being matched against the policy. This is explicitly a regression-class follow-up to CVE-2026-39852, which only stripped literal semicolons and missed percent-encoded variants and encoded slash/backslash traversal into static resource handlers.
Know when Quarkus gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Remote unauthenticated HTTP request with no user interaction; bypass exposes protected resources (C:H) but the advisory describes read access only, so I:N/A:N.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Quarkus is a Java framework for building cloud-native applications. Prior to versions 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2, Quarkus HTTP path-based authorization policies can be bypassed using encoded semicolons (%3B) to smuggle matrix parameters past the security layer, and using encoded slashes (%2F) or backslashes (%5C) to access protected static resources. This is a distinct issue from CVE-2026-39852, which addressed only literal semicolon stripping. Versions 3.37.0, 3.36.3, 3.33.2.1, 3.33.3, 3.27.4.1, 3.27.5, and 3.20.6.2 contain a patch.
Blast Radius
ecosystem impact- 121 maven packages depend on io.quarkus:quarkus-vertx-http (31 direct, 90 indirect)
Ecosystem-wide dependent count for version 3.21.0.CR1.
Articles & Coverage 1
Executive ViewAI
Quarkus Java framework contains a critical vulnerability that permits unauthenticated users to bypass security controls and access protected application resources without authorization. Business applications relying on Quarkus for access control face immediate risk of unauthorized data exposure and potential system compromise. Organizations must urgently assess their Quarkus deployments and deploy interim protections.
Implement WAF rules blocking encoded semicolons (%3B), slashes (%2F), and backslashes (%5C) in URL paths; disable or restrict matrix parameters in Quarkus configuration if not required for application functionality; add additional authentication layers beyond path-based authorization policies; enable comprehensive logging and monitoring for requests containing encoded URL components; implement network segmentation to limit exposure of protected resources.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. Rated high seve
It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavio
Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surpris
A flaw was found in Quarkus. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack comp
A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly whe
In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeseriali
In FasterXML jackson-databind before versions 2.13.4.1 and 2.12.17.1, resource exhaustion can occur because of a lack of
In Gradle before version 7.0, on Unix-like systems, the system temporary directory can be created with open permissions
In Gradle from version 5.1 and before version 7.0 there is a vulnerability which can lead to information disclosure and/
Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable h
A vulnerability was found in quarkus. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no
Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable h
Exploit-DB