Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-434m-5hcj-pxf3 | GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications |
Wed, 28 Oct 2026 21:00:00 +0000
| 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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-28T20:41:47.228Z
Reserved: 2026-10-28T17:25:37.562Z
Link: CVE-2026-118665
No data.
Status : Received
Published: 2026-10-28T21:16:56.827
Modified: 2026-10-28T21:16:56.827
Link: CVE-2026-118665
No data.
OpenCVE Enrichment
Updated: 2026-10-28T22:30:12Z
Github GHSA