Quarkus: graphql operations over websockets bypass (CVE-2023-6394) | HOL Guard CVE

High · CVSS 7.4CVE-2023-6394

Quarkus: graphql operations over websockets bypass

Answer in brief

CVE-2023-6394 records a High severity (CVSS 7.4) vulnerability in Quarkus: graphql operations over websockets bypass. The current sources do not mark it as known exploited. Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Dec 9, 2023Updated Sep 29, 2026Source checked Sep 29, 2026First seen by HOL Sep 29, 2026Material review Sep 29, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.4
Exploitation: Not marked as known exploited
Affected software: Not mapped
Fix availability: Not reported

Why this deserves its current priority

CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Dec 9, 2023
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 29, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.