{"answers":{"affected":"2 open source packages ship an affected version, including @graphql-tools/executor-legacy-ws.","exploited":"There is no known exploitation of CVE-2026-103921 in the wild and no public exploit code.","fix":"Upgrade @graphql-tools/executor-legacy-ws to 1.1.35 or later.","what":"CVE-2026-103921 is a high-severity vulnerability in @graphql-tools executor-legacy-ws, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103921 and fix it if it is affected.\n\nWhat it is: CVE-2026-103921 is a high-severity vulnerability in @graphql-tools executor-legacy-ws, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103921 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @graphql-tools/executor-legacy-ws (npm): affected all versions; fixed in 1.1.35\n- @graphql-tools/executor-legacy-ws (npm): affected all versions; fixed in 1.1.35\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-103921/ (Markdown: https://insights.sbomify.com/CVE-2026-103921/index.md)","id":"CVE-2026-103921","markdown":"https://insights.sbomify.com/CVE-2026-103921/index.md","name":"CVE-2026-103921","record":{"aliases":["CLSA-2026-1793113102","GHSA-6fw5-9hq8-w87g","ROOT-APP-NPM-CVE-2026-103921"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GraphQL tools library","requires_auth":"none","summary":"A network attacker can intercept GraphQL WebSocket connections to steal authentication tokens and modify subscription data due to disabled TLS certificate validation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor","id":"CVE-2026-103921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Capacitor Android and iOS: remote content can be loaded at the app origin via the internal HTTP proxy path","id":"CVE-2026-103922"},"packages":[{"ecosystem":"npm","fixed":["1.1.35"],"introduced":["0"],"last_affected":[],"package":"@graphql-tools/executor-legacy-ws","purl":null,"source":"GHSA-6fw5-9hq8-w87g"},{"ecosystem":"npm","fixed":["1.1.35"],"introduced":["0"],"last_affected":[],"package":"@graphql-tools/executor-legacy-ws","purl":"pkg:npm/%40graphql-tools/executor-legacy-ws","source":"GHSA-6fw5-9hq8-w87g"}],"prev":{"headline":"@orpc/zod: Prototype injection in smart coercion","id":"CVE-2026-103918"},"products":["executor-legacy-ws","graphql-tools"],"published":"2026-10-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["@graphql-tools","ardatan"]},"summary":"A network attacker can intercept GraphQL WebSocket connections to steal authentication tokens and modify subscription data due to disabled TLS certificate validation.","url":"https://insights.sbomify.com/CVE-2026-103921/"}