Sign in Sign up
JA · EN · FR
SecPulse
← Back
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.

AI summary snake-internal / snake-material-v2

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
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. Run `grep -r 'io.quarkus:quarkus-vertx-http' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify 
    grep -r 'io.quarkus:quarkus-vertx-http' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.quarkus:quarkus-vertx-http` を grep し、稼働しているサービス・バージョンを把握する。

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

    ステージング環境で 3.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

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

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →