Technical impact
GraphQL Tools’ legacy WebSocket executor retains per‑request connection parameters in a closure‑scoped object after a connection is closed. When the same executor is reused for multiple authorization contexts, a later request that omits a sensitive key can cause the executor to send the previous caller’s Authorization or tenant value in its connection_init payload. This results in the downstream server authenticating the new requester as the earlier user, effectively hijacking authentication. The primary weakness is misuse of stored data across requests, as indicated by CWE‑488 and CWE‑613. The likely attack vector is a malicious or compromised client that can influence connection_init packets, or an upstream component that is able to send arbitrary payloads; this inference is drawn from the description’s explanation of how missing sensitive keys lead to credential reuse.
Affected Systems
The vulnerability affects the @graphql-tools:executor-legacy-ws and ardatan:graphql-tools packages. Any application that uses the legacy WebSocket executor and does not create a new executor instance for each request is susceptible. All versions prior to 1.1.36 are affected; the fix was incorporated in the 1.1.36 release. Applications that already instantiate a fresh executor per request are not impacted.
Risk and Exploitability
The CVSS score is 8.2, indicating high severity. The EPSS score is <1%, implying a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. While no publicly disclosed exploit exists yet, the flaw enables attackers who can craft or influence the connection_init payload to hijack authentication for any subsequent user that shares the executor. Because the vulnerable code path is part of a widely used GraphQL library, the potential impact is broad, affecting all deployments that reuse executors across different authorization contexts.
Github GHSA