CVE Intelligence
Critical Access control

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

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.

Published Dec 8, 2023 · Updated Oct 20, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.8% (30-day exploitation probability)+8
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.81%
ahead of 56% of scored CVEs · Oct 19, 2026
Affects
Quarkus
Quarkus and 3 more
CVSS base
9.1
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Io.quarkus:quarkus-smallrye-graphql-client: fixed in version 3.5.3 — github.com (GitHub Security Advisories)
  • Maven Io.quarkus:quarkus-smallrye-graphql-client: fixed in version 2.13.9.Final — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Quarkus Quarkus, Red Hat Build Of Quarkus, Red Hat Red Hat build of Quarkus 3.2.9.Final…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Quarkus Quarkus < 3.6.0 Vulnerable NIST National Vulnerability Database
Red Hat Build Of Quarkus versions not specified by the source Vulnerable NIST National Vulnerability Database
Red Hat Build Of Quarkus versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat build of Quarkus 3.2.9.Final versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Maven Io.quarkus:quarkus-smallrye-graphql-client ≥ 2.14.0 and < 3.5.3< 2.13.9.Final Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.1 CVSS 3.1 Critical 3.9 5.2 nvd@nist.gov via NIST National Vulnerability Database
7.4 CVSS 3.1 High 2.2 5.2 secalert@redhat.com via NIST National Vulnerability Database
7.4 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.4 CVSS 3.1 High — — redhat via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.1 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-862 · Missing Authorization

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 20, 2026 · GitHub Security Advisories
  • Affected products added · maven/io.quarkus:quarkus-smallrye-graphql-client
    Oct 20, 2026 · GitHub Security Advisories
  • Affected products added · red hat/red hat build of quarkus 3.2.9.final, red hat/red hat build of quarkus
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 20, 2026
  • Affected products added · quarkus/quarkus, redhat/build of quarkus
    Oct 20, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.1
    Oct 20, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 20, 2026 · Alertas do Telegram
  • 2023
  • CVE published
    Dec 8, 2023 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 20, 2026 – Oct 20, 2026
  • 1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

9 on the record

Elsewhere on this site

Quarkus
every CVE for this vendor
Access control
same class
CWE-862
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-93432 Io.quarkus.qute:quarkus-core: cross-site scripting (xss) and json injection via qute {#eval} section in quarkus Sep 18, 2026
  • CVE-2026-10832 Org.wildfly.security/wildfly-elytron-asn1: unbounded memory allocation in wildfly elytron asn.1 derdecoder via crafted der payload Sep 18, 2026
  • CVE-2026-81829 Smallrye-jwt: quarkus-smallrye-jwt: smallrye-jwt: unauthenticated same-origin ssrf via unsanitized jwt kid header in awsalbkeyresolver Sep 17, 2026
  • CVE-2026-50559 Authentication/Authorization Bypass via Advanced Path Normalization Vulnerabilities Jun 19, 2026
  • CVE-2026-39852 Quarkus authorization bypass via semicolon path normalization inconsistency May 5, 2026
  • CVE-2025-66560 Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write Jan 7, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-6394 is "Quarkus: graphql operations over websockets bypass", rated Critical. It affects Quarkus (Quarkus); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 0.81% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.