CVE-2023-6394 is a high-severity (CVSS 7.4) CWE-862 vulnerability in io.quarkus:quarkus-smallrye-graphql-client. A fix is available for io.quarkus:quarkus-smallrye-graphql-client — see the affected versions and patch details below.
Quarkus: graphql operations over websockets bypass
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-6394.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.quarkus:quarkus-smallrye-graphql-client☕io.quarkus:quarkus-smallrye-graphql-clientReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-smallrye-graphql-client | ≥ 2.14.0&&< 3.5.3 | 3.5.3io.quarkus:quarkus-smallrye-graphql-client:3.5.3 |
| ☕Maven | io.quarkus:quarkus-smallrye-graphql-client | all versions | 2.13.9.Finalio.quarkus:quarkus-smallrye-graphql-client:2.13.9.Final |
Affected Products
quarkusquarkusbuild of quarkusredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-smallrye-graphql-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Quarkus 2.13.9 | see advisory | RHSA-2023:7700 |
| Red Hat build of Quarkus 3.2.9.Final | io.quarkus/quarkus-smallrye-graphql:3.2.9.Final-redhat-00002 | RHSA-2023:7612 |
Frequently Asked Questions
Is CVE-2023-6394 in your dependencies?
Find it across Maven, including transitive dependencies.