Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-39852 high CVSS 8.2

Authorization Flaw in io.quarkus:quarkus-vertx-http (CVE-2026-39852)

Summary

Vulnerability in io.quarkus:quarkus-vertx-http (CVE-2026-39852). Confidential information can be exposed externally. Mitigation: upgrade to 3.35.1.1 or later.

Original description

The description as published by the source.

Quarkus version 3.32.4 is vulnerable to an authorization bypass issue (GHSL-2026-099), in which semicolons (matrix parameters) in HTTP requests can be used to bypass security constraints, potentially allowing unauthorized access to protected resources.

Unauthenticated or lower-privileged users can bypass HTTP path-based authorization policies by appending a semicolon (;) and arbitrary text to the request URL. The vulnerability arises from a path-normalization inconsistency: Quarkus's security layer performs authorization checks on the raw URL path (which preserves matrix parameters), whereas RESTEasy Reactive's routing layer strips matrix parameters before matching endpoints. This allows requests like /api/admin;anything to bypass policies protecting /api/admin while still routing to the protected endpoint.

Impact

This issue may lead to Authentication/Authorization bypasses.

Credits

This issue was discovered with the GitHub Security Lab Taskflow Agent and manually verified by GHSL team members @p- (Peter Stöckli) and @m-y-mo (Man Yue Mo).

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-39852 has been found in io.quarkus:quarkus-vertx-http.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade io.quarkus:quarkus-vertx-http to 3.35.1.1 or later.
If unsure, ask your IT team or search "io.quarkus:quarkus-vertx-http CVE-2026-39852" on the vendor's site.

CVE-2026-39852 (io.quarkus:quarkus-vertx-http) — CWE-863 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.35.1.1 — 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

Incorrect authorization (CWE-863) exists in io.quarkus:quarkus-vertx-http.

📍 Affected scope

Check the vendor advisory for the affected versions of io.quarkus:quarkus-vertx-http.

🔥 Severity

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

🔧 How to fix

Update to 3.35.1.1.

🛡️ 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.35.1.1

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

  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.35.1.1"}]}]

References

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