Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 01 Oct 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 01 Oct 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor | |
| Weaknesses | CWE-295 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-01T18:04:28.083Z
Reserved: 2026-10-01T14:20:19.154Z
Link: CVE-2026-103921
Updated: 2026-10-01T18:04:19.347Z
Status : Received
Published: 2026-10-01T17:17:19.390
Modified: 2026-10-01T19:17:18.647
Link: CVE-2026-103921
No data.
OpenCVE Enrichment
Updated: 2026-10-01T17:30:10Z