Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-103921 high CVSS 7.4

Vulnerability in @graphql-tools/executor-legacy-ws (CVE-2026-103921)

Summary

Vulnerability in @graphql-tools/executor-legacy-ws (CVE-2026-103921). Confidential information can be exposed externally. Exploitable via connectionParams. Mitigation: upgrade to 1.1.35 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-103921 has been found in @graphql-tools/executor-legacy-ws.
Attackers can target a specific entry point like connectionParams over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade @graphql-tools/executor-legacy-ws to 1.1.35 or later.
If unsure, ask your IT team or search "@graphql-tools/executor-legacy-ws CVE-2026-103921" on the vendor's site.

CVE-2026-103921 (@graphql-tools/executor-legacy-ws) — CWE-295 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: connectionParams / headers / SubscriptionProtocol.LEGACY_WS / SubscriptionProtocol.WS
Patched: 1.1.35 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-295) exists in @graphql-tools/executor-legacy-ws. Attackers reach the vulnerable code path via connectionParams without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @graphql-tools/executor-legacy-ws. Attack surface: connectionParams / headers / SubscriptionProtocol.LEGACY_WS / SubscriptionProtocol.WS.

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.1.35.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@graphql-tools/executor-legacy-ws' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@graphql-tools/executor-legacy-ws' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @graphql-tools/executor-legacy-ws を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @graphql-tools/executor-legacy-ws to 1.1.35

    ステージング環境で 1.1.35 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @graphql-tools/executor-legacy-ws
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.35"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details