Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2023-4853

HIGH

CVE-2023-4853 is a high-severity (CVSS 8.1) CWE-148 vulnerability in io.quarkus:quarkus-vertx-http. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2023-4853 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Quarkus: http security policy bypass

Also known asGHSA-4f4r-wgv2-jjvg
Published
Sep 20, 2023
Updated
Aug 6, 2026
Affected
12 pkgs
Patched
12 / 12
Exploits
1 known

Real-World Exposure

12 pkgs affected
io.quarkus:quarkus-vertx-httpio.quarkus:quarkus-vertx-httpio.quarkus:quarkus-vertx-httpio.quarkus:quarkus-undertowio.quarkus:quarkus-undertowio.quarkus:quarkus-undertowio.quarkus:quarkus-csrf-reactiveio.quarkus:quarkus-csrf-reactive+4 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service.

Affected Packages

12 total 12 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.quarkus:quarkus-vertx-httpall versions2.16.11.Final
Mavenio.quarkus:quarkus-vertx-http3.0.0&&< 3.2.6.Final3.2.6.Final
Mavenio.quarkus:quarkus-vertx-http3.3.0&&< 3.3.33.3.3
Mavenio.quarkus:quarkus-undertowall versions2.16.11.Final
Mavenio.quarkus:quarkus-undertow3.0.0&&< 3.2.6.Final3.2.6.Final
Mavenio.quarkus:quarkus-undertow3.3.0&&< 3.3.33.3.3
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-vertx-http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update io.quarkus:quarkus-vertx-http to 2.16.11.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-4853 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-4853 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-4853. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service.
O3 Security · Impact-Aware SCA

Is CVE-2023-4853 in your dependencies?

O3 detects CVE-2023-4853 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.