CVE-2026-103921: high-severity vulnerability in @graphql-tools executor-legacy-ws
GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.4epss 0.3%
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to 1.1.35, the executor-legacy-ws buildWSLegacyExecutor() function hardcodes TLS certificate rejection off for Node.js connections to wss:// endpoints. Applications using the executor directly, or url-loader with SubscriptionProtocol.LEGACY_WS, can therefore accept an attacker-controlled certificate when a network-positioned attacker intercepts the connection. Authentication material in connectionParams or headers can be disclosed, and subscription data can be modified. Browser WebSocket clients are unaffected because browsers enforce certificate validation. This issue is fixed in version 1.1.35.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Related CVEs — @graphql-tools executor-legacy-ws
In the same product, most dangerous first.
CVE-2026-114604HIGHGraphQL Tools: Prototype pollution in mergeIncrementalResult via non-primitive path segmentsEPSS 0.6%CVE-2026-118665HIGHGraphQL Tools: Per-request connection parameters persist into later users' WebSocket authenticationsEPSS 0.5%CVE-2026-104852HIGHGraphQL Tools has prototype pollution in well-established utility function `mergeDeep`EPSS 0.5%CVE-2026-118666MEDIUMGraphQL Tools: Shared legacy executor routes one subscription's results to a different callerEPSS 0.4%
References
https://github.com/ardatan/graphql-tools/commit/3831a0661514c91d99971052f983552556880402https://github.com/ardatan/graphql-tools/pull/8426https://github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/executor-legacy-ws@1.1.35https://github.com/ardatan/graphql-tools/security/advisories/GHSA-6fw5-9hq8-w87g