CVE-2026-50559: Quarkus Authentication/Authorization Bypass Vulnerability

HIGH
Advisory Identifier: GHSA-qcxp-gm7m-4j5v
Advisory Summary

CVE-2026-50559 is a HIGH (CVSS 7.5) authentication/authorization bypass vulnerability (CWE-41: Improper Resolution of Path Equivalence) affecting Quarkus libraries in the Maven ecosystem. The issue involves authentication/authorization bypass via advanced path normalization vulnerabilities. Remediation is available by upgrading affected packages to version 3.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0.

CVE-2026-50559 at a Glance

CVE Identifier CVE-2026-50559
GHSA Identifier GHSA-qcxp-gm7m-4j5v
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-41: Improper Resolution of Path Equivalence
Affected Product Quarkus
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-50559

To remediate this vulnerability, upgrade all affected Quarkus dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.quarkus:quarkus-vertx-http fixed: 3.20.6.2
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx-http</artifactId>
    <version>3.20.6.2</version>
</dependency>
io.quarkus:quarkus-vertx-http fixed: 3.27.4.1
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx-http</artifactId>
    <version>3.27.4.1</version>
</dependency>
io.quarkus:quarkus-vertx-http fixed: 3.33.2.1
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx-http</artifactId>
    <version>3.33.2.1</version>
</dependency>
io.quarkus:quarkus-vertx-http fixed: 3.36.3
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx-http</artifactId>
    <version>3.36.3</version>
</dependency>
io.quarkus:quarkus-vertx-http fixed: 3.37.0
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-vertx-http</artifactId>
    <version>3.37.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.quarkus

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-50559, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.quarkus

Analyze the terminal output to locate any version of Quarkus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.20.6.2), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.quarkus command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-41: Improper Resolution of Path Equivalence, where the product is vulnerable to file system contents disclosure through path equivalence. path equivalence involves the use of special characters in file and directory names. the associated manipulations are intended to generate multiple names for the same object. In Quarkus, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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. ### Technical Details The security layer (AbstractPathMatchingHttpSecurityPolicy) normalizes request paths using Vert.x's normalizedPath(), which only decodes unreserved RFC 3986 characters (letters, digits, -, ., _, ~). It then strips matrix parameters by looking for literal ; characters. This creates two mismatches: 1. Encoded semicolons (`%3B`): Since `%3B` is not decoded by normalizedPath(), the matrix parameter stripping in pathWithoutMatrixParams() never sees it. The encoded semicolon and everything after it become part of the path segment, causing policy matching to fail. This affects all path-policy-protected endpoints. 2. Static resource path mismatch: Static resource handlers (StaticHandlerImpl, FileSystemStaticHandler) perform full percent-decoding via URIDecoder.decodeURIComponent() and backslash-to-slash conversion before filesystem resolution. Reserved characters like `%2F` (slash) and `%5C` (backslash) that survive the security layer's partial decoding are fully decoded before file serving. REST endpoints using Quarkus REST (RESTEasy Reactive) are not affected by the `%2F/%5C` vectors because the routing layer also uses `normalizedPath()` — both security and routing agree on the path, so no mismatch exists. ### Attack Vectors Encoded semicolon (matrix parameter smuggling), affects all path-policy-protected endpoints: - `/api/admin%3Bbypass=true/data`: security sees this as a single segment `admin%3Bbypass=true`, which does not match the `/api/admin/* policy`. The request passes through unauthenticated. - `/api/secret%3b/data`: same mechanism with lowercase hex digit. Encoded slash/backslash on static resources, affects static files behind path policies: - `/static-secret%2Fhtml`, security does not match /static-secret.html policy; static handler decodes `%2F` to `/` and may resolve the file. - `/static-secret%5Chtml `. static handler decodes `%5C` to `\`, then converts to `/`. Double encoding, affects static resources: - `/secret%252Fconfidential.html`, first decode by normalizedPath() turns `%25` into `%`, producing `%2F`. Static handler's second decode turns `%2F` into `/`. The following vectors were investigated and confirmed not exploitable: - Unreserved character encoding (`/api/adm%69n/data`): `normalizedPath()` decodes these. Both security and routing see `/api/admin/data`. - Null byte injection (`/api/admin%00/data`): `%00` is not decoded by `normalizedPath()`. - Encoded dot segments (`/api/%2e%2e/secret/data`): Period is unreserved, so `%2e` is decoded to `.` by `normalizedPath()`, then `removeDots()` normalizes `..` segments. - REST endpoint bypass via `%2F/%5C`: Routing uses the same `normalizedPath()` as security. The encoded slash/backslash doesn't match any route. ### Root Cause `pathWithoutMatrixParams()` operates on the partially-decoded output of `normalizedPath()`, where reserved characters remain encoded. It searches for literal ; but never sees `%3B.` The fix (`normalizePath()`) performs full percent-decoding in a loop before stripping matrix parameters, removing null bytes, normalizing backslashes, and resolving dot segments, aligning the security layer's view of the path with what downstream handlers resolve. ### 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 ### Proof of Concept ``` # Encoded semicolon bypass — works on any path-policy-protected endpoint # Security sees "/api/admin%3Bbypass=true/data", doesn't match /api/admin/* policy curl -v http://target/api/admin%3Bbypass=true/data # Encoded semicolon on authenticated endpoint curl -v http://target/api/secret%3b/data # Static resource bypass via encoded slash (if static file behind path policy) curl -v http://target/static-secret%2Fhtml # Static resource bypass via encoded backslash curl -v http://target/static-secret%5Chtml ```

CVE-2026-50559 Affected Quarkus Versions

5 component(s)
Fixed Versions:
3.20.6.23.27.4.13.33.2.13.36.33.37.0
Product / Package Ecosystem Affected Versions Fixed Version
io.quarkus:quarkus-vertx-http
Maven
< 3.20.6.2
3.20.6.2
io.quarkus:quarkus-vertx-http
Maven
≥ 3.21.0.CR1
< 3.27.4.1
3.27.4.1
io.quarkus:quarkus-vertx-http
Maven
≥ 3.28.0.CR1
< 3.33.2.1
3.33.2.1
io.quarkus:quarkus-vertx-http
Maven
≥ 3.34.0.CR1
< 3.36.3
3.36.3
io.quarkus:quarkus-vertx-http
Maven
≥ 3.37.0.CR1
< 3.37.0
3.37.0

References

Frequently Asked Questions

What is CVE-2026-50559?
CVE-2026-50559 is a security vulnerability in Quarkus involving Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities under CWE-41: Improper Resolution of Path Equivalence.
Which Quarkus versions are affected?
Affected versions include releases prior to 3.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0 across affected packages: io.quarkus:quarkus-vertx-http.
What version fixes CVE-2026-50559?
Upgrading to 3.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is quarkus-vertx-http affected?
Yes, io.quarkus:quarkus-vertx-http is affected in releases prior to 3.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0. Upgrade your dependency to 3.20.6.2, 3.27.4.1, 3.33.2.1, 3.36.3, 3.37.0 or later.
What is the CVSS score of CVE-2026-50559?
CVE-2026-50559 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-50559?
CVE-2026-50559 is classified under CWE-41: Improper Resolution of Path Equivalence (The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.).
How can I check Maven dependencies for CVE-2026-50559?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.quarkus'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qcxp-gm7m-4j5v",
  "modified" : "2026-07-30T12:32:16Z",
  "published" : "2026-07-29T15:40:05Z",
  "aliases" : [ "CVE-2026-50559" ],
  "summary" : "Quarkus: Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities",
  "details" : "Quarkus HTTP path-based authorization policies can be bypassed using encoded semicolons (%3B) to smuggle matrix\n  parameters past the security layer, and using encoded slashes (%2F) or backslashes (%5C) to access protected static\n  resources. This is a distinct issue from CVE-2026-39852, which addressed only literal semicolon stripping.\n\n  ### Technical Details\n\n  The security layer (AbstractPathMatchingHttpSecurityPolicy) normalizes request paths using Vert.x's normalizedPath(),\n  which only decodes unreserved RFC 3986 characters (letters, digits, -, ., _, ~). It then strips matrix parameters by\n  looking for literal ; characters. This creates two mismatches:\n\n  1. Encoded semicolons (`%3B`): Since `%3B` is not decoded by normalizedPath(), the matrix parameter stripping in\n  pathWithoutMatrixParams() never sees it. The encoded semicolon and everything after it become part of the path\n  segment, causing policy matching to fail. This affects all path-policy-protected endpoints.\n  2. Static resource path mismatch: Static resource handlers (StaticHandlerImpl, FileSystemStaticHandler) perform full\n  percent-decoding via URIDecoder.decodeURIComponent() and backslash-to-slash conversion before filesystem resolution.\n  Reserved characters like `%2F` (slash) and `%5C` (backslash) that survive the security layer's partial decoding are fully\n  decoded before file serving.\n\n  REST endpoints using Quarkus REST (RESTEasy Reactive) are not affected by the `%2F/%5C` vectors because the routing layer also uses `normalizedPath()` — both security and routing agree on the path, so no mismatch exists.\n\n###  Attack Vectors\n\n  Encoded semicolon (matrix parameter smuggling), affects all path-policy-protected endpoints:\n  \n  - `/api/admin%3Bbypass=true/data`: security sees this as a single segment `admin%3Bbypass=true`, which does not match the\n   `/api/admin/* policy`. The request passes through unauthenticated.\n  - `/api/secret%3b/data`: same mechanism with lowercase hex digit.\n\n  Encoded slash/backslash on static resources, affects static files behind path policies:\n  - `/static-secret%2Fhtml`, security does not match /static-secret.html policy; static handler decodes `%2F` to `/` and may\n  resolve the file.\n  - `/static-secret%5Chtml `. static handler decodes `%5C` to `\\`, then converts to `/`.\n\n  Double encoding, affects static resources:\n  - `/secret%252Fconfidential.html`, first decode by normalizedPath() turns `%25` into `%`, producing `%2F`. Static handler's\n  second decode turns `%2F` into `/`.\n\n  The following vectors were investigated and confirmed not exploitable:\n\n  - Unreserved character encoding (`/api/adm%69n/data`): `normalizedPath()` decodes these. Both security and routing see\n  `/api/admin/data`. \n  - Null byte injection (`/api/admin%00/data`): `%00` is not decoded by `normalizedPath()`. \n  - Encoded dot segments (`/api/%2e%2e/secret/data`): Period is unreserved, so `%2e` is decoded to `.` by `normalizedPath()`,\n  then `removeDots()` normalizes `..` segments. \n  - REST endpoint bypass via `%2F/%5C`: Routing uses the same `normalizedPath()` as security. The encoded slash/backslash\n  doesn't match any route. \n\n###   Root Cause\n\n  `pathWithoutMatrixParams()` operates on the partially-decoded output of `normalizedPath()`, where reserved characters\n  remain encoded. It searches for literal ; but never sees `%3B.` The fix (`normalizePath()`) performs full percent-decoding\n   in a loop before stripping matrix parameters, removing null bytes, normalizing backslashes, and resolving dot\n  segments, aligning the security layer's view of the path with what downstream handlers resolve.\n\n###  Impact\n\n  - Unauthenticated access to endpoints protected by `quarkus.http.auth.permission` path-based policies via `%3B` smuggling\n  - Static resource exposure by bypassing path policies on protected files via `%2F/%5C`\n  - Applications using annotation-based security (`@RolesAllowed`, `@Authenticated`) on JAX-RS resources without path-based\n  policies are not affected by the `%2F/%5C` vectors, but may still be affected by `%3B` if path policies coexist\n\n###  Proof of Concept\n\n```\n  # Encoded semicolon bypass — works on any path-policy-protected endpoint\n  # Security sees \"/api/admin%3Bbypass=true/data\", doesn't match /api/admin/* policy\n  curl -v http://target/api/admin%3Bbypass=true/data\n\n  # Encoded semicolon on authenticated endpoint\n  curl -v http://target/api/secret%3b/data\n\n  # Static resource bypass via encoded slash (if static file behind path policy)\n  curl -v http://target/static-secret%2Fhtml\n\n  # Static resource bypass via encoded backslash\n  curl -v http://target/static-secret%5Chtml\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx-http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.20.6.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx-http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.21.0.CR1"
      }, {
        "fixed" : "3.27.4.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx-http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.28.0.CR1"
      }, {
        "fixed" : "3.33.2.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx-http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.34.0.CR1"
      }, {
        "fixed" : "3.36.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.quarkus:quarkus-vertx-http"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.37.0.CR1"
      }, {
        "fixed" : "3.37.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/security/advisories/GHSA-qcxp-gm7m-4j5v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-50559"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quarkusio/quarkus/commit/919b80017d85564143a845b38e9cca54aff5b3cc"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:26017"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:26018"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:26194"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:26586"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:34608"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:36820"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:48151"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-50559"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2486959"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/quarkusio/quarkus"
  }, {
    "type" : "WEB",
    "url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-50559.json"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-178", "CWE-287", "CWE-41", "CWE-551", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-29T15:40:05Z",
    "nvd_published_at" : "2026-06-19T21:17:02Z"
  }
}