# CVE-2026-39852: Quarkus authorization bypass via semicolon path normalization inconsistency > Attackers can bypass path-based authorization policies in Quarkus applications by appending semicolons to URLs, accessing protected endpoints without proper credentials. - **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 May 2026 - **Updated:** 17 Aug 2026 - **Also known as:** CLEANSTART-2026-CY16294, CLEANSTART-2026-QF31324, CLEANSTART-2026-SH82729, ECHO-7228-fbde-6e25, GHSA-rc95-pcm8-65v9, MINI-jc6v-6f3m-98c2, MINI-m269-qh6j-hv5q, MINI-m2mf-36r4-2fvf, MINI-wcpr-p4qv-28wq ## What is CVE-2026-39852? CVE-2026-39852 is a high-severity authentication bypass vulnerability in quarkusio quarkus, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Quarkus is a Java framework for building cloud-native applications. In versions prior to 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, and 3.35.2, a path normalization inconsistency between the security layer and the routing layer allows unauthenticated or lower-privileged users to bypass HTTP path-based authorization policies. Quarkus's security layer performs authorization checks on the raw URL path which preserves matrix parameters (semicolons), while RESTEasy Reactive's routing layer strips matrix parameters before matching endpoints. An attacker can append a semicolon and arbitrary text to a request URL (e.g., /api/admin;anything) to bypass policies protecting /api/admin while still routing to the protected endpoint. This issue has been fixed in versions 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, and 3.35.2. Weakness: CWE-551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization), CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-39852? 8 open source packages ship an affected version, including io.quarkus:quarkus-vertx-http. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.quarkus:quarkus-vertx-http` | Maven | All versions | 3.20.6.1 | | `io.quarkus:quarkus-vertx-http` | Maven | All versions | 3.20.6.1 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.21.0 | 3.27.3.1 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.21.0 | 3.27.3.1 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.30.0 | 3.33.1.1 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.30.0 | 3.33.1.1 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.34.0 | 3.35.1.1 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.34.0 | 3.35.1.1 | Products: Quarkus Quarkus. ## How do I fix CVE-2026-39852? Upgrade io.quarkus:quarkus-vertx-http to a fixed version for your release line: 3.20.6.1, 3.27.3.1, 3.33.1.1 or 3.35.1.1. ## Is CVE-2026-39852 being exploited? There is no known exploitation of CVE-2026-39852 in the wild and no public exploit code. ## Other vulnerabilities in quarkusio quarkus - [CVE-2022-4116](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8) - [CVE-2022-2466](https://insights.sbomify.com/CVE-2022-2466/): Quarkus does not terminate HTTP requests header context (critical 9.8) - [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1) - [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8) - [CVE-2023-6267](https://insights.sbomify.com/CVE-2023-6267/): Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations. (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-39852 and fix it if it is affected. What it is: CVE-2026-39852 is a high-severity authentication bypass vulnerability in quarkusio quarkus, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-39852 in the wild and no public exploit code. Affected packages and fixed versions: - io.quarkus:quarkus-vertx-http (Maven): affected all versions; fixed in 3.20.6.1 - io.quarkus:quarkus-vertx-http (Maven): affected all versions; fixed in 3.20.6.1 - io.quarkus:quarkus-vertx-http (Maven): affected from 3.21.0; fixed in 3.27.3.1 - io.quarkus:quarkus-vertx-http (Maven): affected from 3.21.0; fixed in 3.27.3.1 - io.quarkus:quarkus-vertx-http (Maven): affected from 3.30.0; fixed in 3.33.1.1 - io.quarkus:quarkus-vertx-http (Maven): affected from 3.30.0; fixed in 3.33.1.1 - io.quarkus:quarkus-vertx-http (Maven): affected from 3.34.0; fixed in 3.35.1.1 - io.quarkus:quarkus-vertx-http (Maven): affected from 3.34.0; fixed in 3.35.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-39852/ (Markdown: https://insights.sbomify.com/CVE-2026-39852/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39852 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39852 - OSV: https://osv.dev/vulnerability/CVE-2026-39852 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-39852/ Summaries are generated and may contain mistakes; the official description above is the record.