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

CVE-2023-6394

HIGH

CVE-2023-6394 is a high-severity (CVSS 7.4) CWE-862 vulnerability in io.quarkus:quarkus-smallrye-graphql-client. O3 Security confirms whether CVE-2023-6394 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Quarkus: graphql operations over websockets bypass

Also known asGHSA-mvc8-6ffp-jrx5
Published
Dec 9, 2023
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
io.quarkus:quarkus-smallrye-graphql-clientio.quarkus:quarkus-smallrye-graphql-client

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. This issue occurs when receiving a request over websocket with no role-based permission specified on the GraphQL operation, Quarkus processes the request without authentication despite the endpoint being secured. This can allow an attacker to access information and functionality outside of normal granted API permissions.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.quarkus:quarkus-smallrye-graphql-client2.14.0&&< 3.5.33.5.3
Mavenio.quarkus:quarkus-smallrye-graphql-clientall versions2.13.9.Final

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-smallrye-graphql-client. 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-smallrye-graphql-client to 3.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6394 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-6394 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-6394. 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. This issue occurs when receiving a request over websocket with no role-based permission specified on the GraphQL operation, Quarkus processes the request without authentication despite the endpoint being secured. This can allow an attacker to access information and functionality outside of normal granted API permissions.
O3 Security · Impact-Aware SCA

Is CVE-2023-6394 in your dependencies?

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