Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-50559 high CVSS 7.5

Authentication Bypass in io.quarkus:quarkus-vertx-http (CVE-2026-50559)

Summary

Authentication bypass in io.quarkus:quarkus-vertx-http (CVE-2026-50559). Confidential information can be exposed externally. Exploitable via quarkus.http.auth.permission. Mitigation: upgrade to 3.37.0 or later.

Original description

The description as published by the source.

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 rout…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-50559 has been found in io.quarkus:quarkus-vertx-http.
Attackers can target a specific entry point like quarkus.http.auth.permission over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade io.quarkus:quarkus-vertx-http to 3.37.0 or later.
If unsure, ask your IT team or search "io.quarkus:quarkus-vertx-http CVE-2026-50559" on the vendor's site.

CVE-2026-50559 (io.quarkus:quarkus-vertx-http) — CWE-287 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: quarkus.http.auth.permission
Patched: 3.37.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in io.quarkus:quarkus-vertx-http. Attackers reach the vulnerable code path via quarkus.http.auth.permission without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of io.quarkus:quarkus-vertx-http. Attack surface: quarkus.http.auth.permission.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.37.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.quarkus:quarkus-vertx-http を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.quarkus:quarkus-vertx-http to 3.37.0

    ステージング環境で 3.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven io.quarkus:quarkus-vertx-http
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.37.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details