CVE-2026-118665

GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications

Published Oct 28, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
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 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.

Analysis

AI-generated

Technical impact

GraphQL Tools’ legacy WebSocket executor retains per‑request connection parameters in a closure‑scoped object after a connection is closed. When the same executor is reused for multiple authorization contexts, a later request that omits a sensitive key can cause the executor to send the previous caller’s Authorization or tenant value in its connection_init payload. This results in the downstream server authenticating the new requester as the earlier user, effectively hijacking authentication. The primary weakness is misuse of stored data across requests, as indicated by CWE‑488 and CWE‑613. The likely attack vector is a malicious or compromised client that can influence connection_init packets, or an upstream component that is able to send arbitrary payloads; this inference is drawn from the description’s explanation of how missing sensitive keys lead to credential reuse.

Affected Systems

The vulnerability affects the @graphql-tools:executor-legacy-ws and ardatan:graphql-tools packages. Any application that uses the legacy WebSocket executor and does not create a new executor instance for each request is susceptible. All versions prior to 1.1.36 are affected; the fix was incorporated in the 1.1.36 release. Applications that already instantiate a fresh executor per request are not impacted.

Risk and Exploitability

The CVSS score is 8.2, indicating high severity. The EPSS score is <1%, implying a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. While no publicly disclosed exploit exists yet, the flaw enables attackers who can craft or influence the connection_init payload to hijack authentication for any subsequent user that shares the executor. Because the vulnerable code path is part of a widely used GraphQL library, the potential impact is broad, affecting all deployments that reuse executors across different authorization contexts.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the @graphql-tools:executor-legacy-ws package to version 1.1.36 or later.
  • If upgrading is not immediately possible, configure the application to instantiate a new executor for each request to avoid reusing the executor across authorization contexts.
  • As a temporary containment, modify the application to explicitly clear or nullify connectionParams after closing a WebSocket session or to validate that each connection_init payload contains the required authentication information before processing.

Generated by OpenCVE AI on November 6, 2026 at 03:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-434m-5hcj-pxf3 GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications
History
Type Values Removed Values Added
Weaknesses CWE-488
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Ardatan
Ardatan executor-legacy-ws
Ardatan graphql-tools
Vendors & Products Ardatan
Ardatan executor-legacy-ws
Ardatan graphql-tools
Type Values Removed Values Added
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 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.
Title GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications
Weaknesses CWE-613
References
Metrics cvssV4_0

{'score': 8.2, 'vector': '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'}

Weaknesses
  • CWE-488

    Exposure of Data Element to Wrong Session

  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 1:37 PM
Reserved
Oct 28, 2026, 5:25 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 9:16 PM
Modified
Nov 3, 2026, 2:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 8:41 PM