GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor

Why it is Yellow

• CVSS 7.4 high
• Remotely exploitable without logging in
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-6fw5-9hq8-w87g
• https://github.com/ardatan/graphql-tools/security/advisories/GHSA-6fw5-9hq8-w87g
• https://nvd.nist.gov/vuln/detail/CVE-2026-103921
• https://github.com/ardatan/graphql-tools/pull/8426
• https://github.com/ardatan/graphql-tools/commit/3831a0661514c91d99971052f983552556880402
• https://github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/executor-legacy-ws@1.1.35
• https://github.com/advisories/GHSA-6fw5-9hq8-w87g

Original description

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.