CVE-2026-50559

Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities

HIGH
7.5
CVSS Score
Published: June 19, 2026 at 08:26 PM UTC
Updated: October 25, 2026 at 11:10 PM UTC
9 products affected across 3 vendorsQuarkusQuarkusOpenShift AI

Using quarkus by quarkusio?

Get instant alerts when new vulnerabilities affect quarkus - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1%
SSVC
PoC

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.20.6.23.21.0 ≤ v < 3.27.4.13.28.0 ≤ v < 3.33.2.13.34.0 ≤ v < 3.36.3
Affected range stops below 3.20.6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.27.4.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.33.2.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.36.3, so it looks safe — our inference, not a vendor statement
v < 3.20.6.2
Affected range stops below 3.20.6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.27.4.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.33.2.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.36.3, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in vertx-http (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (12)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/quarkusio/quarkus/security/advisories/GHSA-qcxp-gm7m-4j5v
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26017
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26018
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26194
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:26586
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-50559
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2486959

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-287CWE-863CWE-551

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card