CVE-2026-118665: high-severity vulnerability in ardatan graphql-tools
GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications
Published · Updated
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 8.2epss 0.4%
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 retains request.extensions.connectionParams in the closure-scoped executorConnectionParams object after cleanupWebsocket closes a connection. When one executor is reused across different authorization contexts, a later request that omits a sensitive key can send an earlier caller's Authorization or tenant value in its connection_init payload, causing the downstream server to authenticate the later caller as the earlier user. Applications that create a new executor for every request are not affected. This issue is fixed in version 1.1.36 of the GraphQL Tools legacy WebSocket executor package.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Related CVEs — ardatan graphql-tools
In the same product, most dangerous first.
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.3%CVE-2026-103921HIGHGraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket ExecutorEPSS 0.3%
References
https://github.com/ardatan/graphql-tools/commit/c2f226e6f68236be9e4a577f29faeaa92547458bhttps://github.com/ardatan/graphql-tools/pull/8480https://github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/executor-legacy-ws@1.1.36https://github.com/ardatan/graphql-tools/security/advisories/GHSA-434m-5hcj-pxf3