GraphQL Tools: Shared legacy executor routes one subscription's results to a different caller
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.0.36, 1.1.36
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The GraphQL Tools legacy WebSocket executor package (used for building and stitching GraphQL subscriptions) is affected before version 1.1.36. When multiple overlapping subscriptions share one executor, a caller can receive another user's subscription data while the original caller's stream stops receiving updates.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to version 1.1.36 of the GraphQL Tools legacy WebSocket executor package, buildWSLegacyExecutor in packages/executors/legacy-ws/src/index.ts reuses one WebSocket and replaces its single websocket.onmessage handler whenever a new overlapping subscription starts. The handler delivers LEGACY_WS.DATA frames to the newest observer without comparing data.id with the subscription operation id, so a caller using the same executor can receive another user's authorized subscription payload while the earlier caller's stream is starved. This issue is fixed in version 1.1.36 of the GraphQL Tools legacy WebSocket executor package.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ardatan graphql-tools
fixed in 9.0.36
- @graphql-tools executor-legacy-ws
fixed in 1.1.36
- @graphql-tools/executor-legacy-wsnpm
fixed in 1.1.36