Skip to main content
VulnerabilityPublished

CVE-2026-103921: ardatan graphql-tools · Improper Certificate Validation

Affects ardatan graphql-toolsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 1.1.35 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.35
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade graphql-tools and executor-legacy-ws to 1.1.35.

Affected software

ProductAffectedFixed in
ardatangraphql-toolsAffected
  • <1.1.35
Fixed in
  • 1.1.35
@graphql-toolsexecutor-legacy-wsAffected
  • <1.1.35
Fixed in
  • 1.1.35

AI-suggested

Upgrade to graphql-tools version 1.1.35 or later, where TLS certificate validation is properly enforced for Node.js WebSocket connections. Until upgraded, avoid using the executor-legacy-ws or url-loader with SubscriptionProtocol.LEGACY_WS for Node.js WebSocket connections to wss:// endpoints.

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.

References

Community reviews

Loading reviews…