Vulnerabilities in pkg:npm/@graphql-tools/executor-legacy-ws

PACKAGE
Advisory Identifier: GHSA-6fw5-9hq8-w87g
Advisory Summary

CVE-2026-103921 is a HIGH (CVSS 7.4) tls certificate validation disabled vulnerability (CWE-295: Improper Certificate Validation) affecting GraphQL Tools libraries in the npm ecosystem. The issue involves tls certificate validation disabled in legacy graphql websocket executor. Remediation is available by upgrading affected packages to version 1.1.35.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@graphql-tools/executor-legacy-ws

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@graphql-tools/executor-legacy-ws. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-6fw5-9hq8-w87g CVE-2026-103921 HIGH GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor

CVE-2026-103921 at a Glance

CVE Identifier CVE-2026-103921
GHSA Identifier GHSA-6fw5-9hq8-w87g
Severity HIGH
CVSS v3.1 Base Score 7.4
CWE Classification CWE-295: Improper Certificate Validation
Affected Product GraphQL Tools
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-103921

To remediate this vulnerability, upgrade all affected GraphQL Tools dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@graphql-tools/executor-legacy-ws fixed: 1.1.35
npm install @graphql-tools/executor-legacy-ws@1.1.35
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @graphql-tools/executor-legacy-ws

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-103921, inspect your project dependencies using npm:

npm ls @graphql-tools/executor-legacy-ws

Analyze the terminal output to locate any version of GraphQL Tools in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.35), your application is affected.

Note: The npm ls @graphql-tools/executor-legacy-ws command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. In GraphQL Tools, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact `buildWSLegacyExecutor()` in `@graphql-tools/executor-legacy-ws` previously hardcoded `rejectUnauthorized: false` when creating WebSocket connections over WSS. This disabled TLS certificate validation, allowing a network-positioned attacker to perform a Man-in-the-Middle (MITM) attack against applications that use this executor with a `wss://` endpoint. Credentials passed via `connectionParams` or `headers` could be intercepted, and subscription data could be tampered with. **Who is impacted:** Applications using `@graphql-tools/executor-legacy-ws` (directly or via `@graphql-tools/url-loader` with `SubscriptionProtocol.LEGACY_WS`) to connect to a `wss://` endpoint from Node.js while sending authentication material over the connection. Browser WebSocket clients are unaffected by this option (browsers always validate certificates). ## Patches Upgrade to `@graphql-tools/executor-legacy-ws@1.1.35` or later (and `@graphql-tools/url-loader@9.1.9` or later if you use the loader). TLS certificate validation is enabled by default. Callers that intentionally use self-signed certificates in trusted environments can opt out with `rejectUnauthorized: false`. ## Workarounds - Prefer the modern `graphql-ws` / `SubscriptionProtocol.WS` path where possible. - Until upgraded, avoid sending secrets over legacy WSS connections, or terminate TLS at a trusted proxy and use `ws://` only on trusted networks. - Supply a custom `webSocketImpl` that enforces certificate validation.

CVE-2026-103921 Affected GraphQL Tools Versions

1 component(s)
Fixed Versions:
1.1.35
Product / Package Ecosystem Affected Versions Fixed Version
@graphql-tools/executor-legacy-ws
npm
< 1.1.35
1.1.35

References

Frequently Asked Questions

What is CVE-2026-103921?
CVE-2026-103921 is a security vulnerability in GraphQL Tools involving TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor under CWE-295: Improper Certificate Validation.
Which GraphQL Tools versions are affected?
Affected versions include releases prior to 1.1.35 across affected packages: @graphql-tools/executor-legacy-ws.
What version fixes CVE-2026-103921?
Upgrading to 1.1.35 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @graphql-tools/executor-legacy-ws affected?
Yes, @graphql-tools/executor-legacy-ws is affected in releases prior to 1.1.35. Upgrade your dependency to 1.1.35 or later.
What is the CVSS score of CVE-2026-103921?
CVE-2026-103921 has a CVSS v3.1 base score of 7.4 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-103921?
CVE-2026-103921 is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check npm dependencies for CVE-2026-103921?
Run the dependency tree command: 'npm ls @graphql-tools/executor-legacy-ws'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6fw5-9hq8-w87g",
  "modified" : "2026-10-05T22:56:56Z",
  "published" : "2026-10-05T22:56:56Z",
  "aliases" : [ "CVE-2026-103921" ],
  "summary" : "GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor",
  "details" : "## Impact\n\n`buildWSLegacyExecutor()` in `@graphql-tools/executor-legacy-ws` previously hardcoded `rejectUnauthorized: false` when creating WebSocket connections over WSS. This disabled TLS certificate validation, allowing a network-positioned attacker to perform a Man-in-the-Middle (MITM) attack against applications that use this executor with a `wss://` endpoint. Credentials passed via `connectionParams` or `headers` could be intercepted, and subscription data could be tampered with.\n\n**Who is impacted:** Applications using `@graphql-tools/executor-legacy-ws` (directly or via `@graphql-tools/url-loader` with `SubscriptionProtocol.LEGACY_WS`) to connect to a `wss://` endpoint from Node.js while sending authentication material over the connection.\n\nBrowser WebSocket clients are unaffected by this option (browsers always validate certificates).\n\n## Patches\n\nUpgrade to `@graphql-tools/executor-legacy-ws@1.1.35` or later (and `@graphql-tools/url-loader@9.1.9` or later if you use the loader). TLS certificate validation is enabled by default. Callers that intentionally use self-signed certificates in trusted environments can opt out with `rejectUnauthorized: false`.\n\n## Workarounds\n\n- Prefer the modern `graphql-ws` / `SubscriptionProtocol.WS` path where possible.\n- Until upgraded, avoid sending secrets over legacy WSS connections, or terminate TLS at a trusted proxy and use `ws://` only on trusted networks.\n- Supply a custom `webSocketImpl` that enforces certificate validation.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@graphql-tools/executor-legacy-ws"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.1.35"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.1.34"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ardatan/graphql-tools/security/advisories/GHSA-6fw5-9hq8-w87g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-103921"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ardatan/graphql-tools/pull/8426"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ardatan/graphql-tools/commit/3831a0661514c91d99971052f983552556880402"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ardatan/graphql-tools"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/executor-legacy-ws@1.1.35"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-05T22:56:56Z",
    "nvd_published_at" : "2026-10-01T17:17:19Z"
  }
}