Executor Legacy Ws
Approved changes feed: RSS · Atom
cpe:2.3:a:@graphql-tools:executor-legacy-ws:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | @Graphql Tools (be40531c-4606-57c7-8cb0-4a145dcd1888) |
|---|---|
| Product | Executor Legacy Ws (a02dda84-341f-5d9e-9634-169357839bab) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-118665 |
vulnerable | 2026-11-03 10:17:04.526861 |
GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications
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.
Published: 2026-10-28T20:41:47.228Z
Updated: 2026-11-03T13:37:29.132Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-118666 |
vulnerable | 2026-11-03 10:17:04.371392 |
GraphQL Tools: Shared legacy executor routes one subscription's results to a different caller
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 reuses one WebSocket and replaces its single websocket.onmessage handler whenever a new overlapping subscription starts. The handler delivers LEGACY_WS.DATA frames to the newest observer without comparing data.id with the subscription operation id, so a caller using the same executor can receive another user's authorized subscription payload while the earlier caller's stream is starved. This issue is fixed in version 1.1.36 of the GraphQL Tools legacy WebSocket executor package.
Published: 2026-10-28T20:45:58.056Z
Updated: 2026-11-02T23:58:49.472Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.