# CVE-2023-6394: Quarkus: graphql operations over websockets bypass

> Attackers can bypass authentication on secured GraphQL endpoints over WebSockets to access unauthorized data and functionality.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2023
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-mvc8-6ffp-jrx5

## What is CVE-2023-6394?

CVE-2023-6394 is a high-severity missing authorization vulnerability in Red Hat build of Quarkus, published on 9 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-6394?

4 open source packages ship an affected version, including io.quarkus:quarkus-smallrye-graphql-client. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus:quarkus-smallrye-graphql-client` | Maven | All versions | 2.13.9.Final |
| `io.quarkus:quarkus-smallrye-graphql-client` | Maven | All versions | 2.13.9.Final |
| `io.quarkus:quarkus-smallrye-graphql-client` | Maven | From 2.14.0 | 3.5.3 |
| `io.quarkus:quarkus-smallrye-graphql-client` | Maven | From 2.14.0 | 3.5.3 |

Products: Quarkus Quarkus, Redhat Build of Quarkus.

## How do I fix CVE-2023-6394?

Upgrade io.quarkus:quarkus-smallrye-graphql-client to a fixed version for your release line: 2.13.9.Final or 3.5.3.

## Is CVE-2023-6394 being exploited?

There is no known exploitation of CVE-2023-6394 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat build of 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-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8)
- [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6394 and fix it if it is affected.

What it is: CVE-2023-6394 is a high-severity missing authorization vulnerability in Red Hat build of Quarkus, published on 9 Dec 2023. 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-2023-6394 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-smallrye-graphql-client (Maven): affected all versions; fixed in 2.13.9.Final
- io.quarkus:quarkus-smallrye-graphql-client (Maven): affected all versions; fixed in 2.13.9.Final
- io.quarkus:quarkus-smallrye-graphql-client (Maven): affected from 2.14.0; fixed in 3.5.3
- io.quarkus:quarkus-smallrye-graphql-client (Maven): affected from 2.14.0; fixed in 3.5.3

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-2023-6394/ (Markdown: https://insights.sbomify.com/CVE-2023-6394/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6394
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6394
- OSV: https://osv.dev/vulnerability/CVE-2023-6394

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6394/
Summaries are generated and may contain mistakes; the official description above is the record.