Advisory record · GHSA-qcxp-gm7m-4j5v

Quarkus: Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities

CVSS 7.5 HighEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 29 Jul 2026, 15:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.quarkus:quarkus-vertx-httpMaven<3.20.6.2 || >=3.21.0.CR1, <3.27.4.1 || >=3.28.0.CR1, <3.33.2.1 || >=3.34.0.CR1, <3.36.3 || >=3.37.0.CR1, <3.37.03.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0
Identifiers
GHSA-qcxp-gm7m-4j5v · CVE-2026-50559
Weakness (CWE)
CWE-41 · CWE-178 · CWE-287 · CWE-551 · CWE-863
Published
29 Jul 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Quarkus quarkus-vertx-http (Maven io.quarkus:quarkus-vertx-http) versions before 3.20.6.2, from 3.21.0.CR1 before 3.27.4.1, from 3.28.0.CR1 before 3.33.2.1, from 3.34.0.CR1 before 3.36.3, and from 3.37.0.CR1 before 3.37.0 have path-based authorization policies that can be bypassed by sending encoded semicolons, slashes or backslashes in request paths. An unauthenticated remote attacker can reach protected endpoints and static files. Upgrade to 3.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.