Quarkus: Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities
Published Jun 19, 2026 · Updated Oct 23, 2026 · Also known as GHSA-qcxp-gm7m-4j5v
Original summary
Normalized public record · Updated Oct 23, 2026
Quarkus: Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Potential impact
- Unauthenticated access to endpoints protected by quarkus.http.auth.permission path-based policies via %3B smuggling - Static resource exposure by bypassing path policies on protected files via %2F/%5C - Applications using annotation-based security (@RolesAllowed, @Authenticated) on JAX-RS resources without path-based policies are not affected by the %2F/%5C vectors, but may still be affected by %3B if path policies coexist
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 10%
- Aliases
- GHSA-qcxp-gm7m-4j5v
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- Security advisory ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- access.redhat.com ↗
- bugzilla.redhat.com ↗
- security.access.redhat.com ↗
Record history
Published Jun 19, 2026 · Last refreshed Oct 23, 2026