Technical impact
A flaw in the GraphQL Tools legacy WebSocket executor causes it to reuse a single websocket.onmessage handler when new overlapping subscription requests are started. The handler forwards incoming LEGACY_WS.DATA frames directly to the most recent observer without verifying that the data.frame’s id matches the original subscription operation id. As a result, a subscriber can receive another user’s authorized subscription payload while the original subscription stream is stalled, enabling disclosure of protected data. This is a classic example of information disclosure (CWE-200).
Affected Systems
The issue affects applications that use @graphql-tools:executor-legacy-ws or ardatan:graphql-tools at any version prior to 1.1.36. The package release 1.1.36 introduces the fix that properly associates data frames with their subscription id; older versions have no hotfix.
Risk and Exploitability
The CVSS score of 6 indicates moderate severity. EPSS score is < 1%, indicating a very low but non-zero exploitation probability, and the flaw is not listed in the CISA KEV catalog. The likely attack vector is remote, inferred from the nature of WebSocket subscription requests; an attacker would need to set up overlapping subscription requests using the same executor instance to trigger the flaw. If successful, the attacker can access subscription payloads not intended for them, resulting in unauthorized data leakage.
Github GHSA