How severe is GHSA-6fw5-9hq8-w87g?

GHSA-6fw5-9hq8-w87g has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6fw5-9hq8-w87g?

GHSA-6fw5-9hq8-w87g affects the following packages: @graphql-tools/executor-legacy-ws (npm). Ecosystems affected: npm.

How do I fix GHSA-6fw5-9hq8-w87g?

Update @graphql-tools/executor-legacy-ws to 1.1.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fw5-9hq8-w87g is resolved across your whole dependency graph.

How do I detect GHSA-6fw5-9hq8-w87g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @graphql-tools/executor-legacy-ws, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6fw5-9hq8-w87g if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6fw5-9hq8-w87g actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fw5-9hq8-w87g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6fw5-9hq8-w87g?

GHSA-6fw5-9hq8-w87g has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6fw5-9hq8-w87g?

GHSA-6fw5-9hq8-w87g is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6fw5-9hq8-w87g published, and has it been updated?

GHSA-6fw5-9hq8-w87g was published on October 5, 2026 and was last updated on October 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket ExecutorGHSA-6fw5-9hq8-w87g

HIGHFix: ardatan/graphql-tools#8426

GHSA-6fw5-9hq8-w87g is a high-severity (CVSS 7.4) CWE-295 vulnerability in @graphql-tools/executor-legacy-ws. A fix is available for @graphql-tools/executor-legacy-ws — see the affected versions and patch details below.

Also known asCVE-2026-103921

Published

Oct 5, 2026

Updated

Oct 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6fw5-9hq8-w87g.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-6fw5-9hq8-w87g by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

📦@graphql-tools/executor-legacy-ws

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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/[email protected] or later (and @graphql-tools/[email protected] 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@graphql-tools/executor-legacy-ws`	all versions	1.1.35`npm install @graphql-tools/executor-legacy-ws@1.1.35`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @graphql-tools/executor-legacy-ws, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @graphql-tools/executor-legacy-ws to 1.1.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fw5-9hq8-w87g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 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/