cve.bz

CVE-2026-118665 Insufficient Session Expiration

8.2 highEPSS 0.4%Fix available

High (8.2). EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @graphql-tools/executor-legacy-ws 1.1.36.

On this page
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to version 1.1.36 of the GraphQL Tools legacy WebSocket executor package, buildWSLegacyExecutor in packages/executors/legacy-ws/src/index.ts retains request.extensions.connectionParams in the closure-scoped executorConnectionParams object after cleanupWebsocket closes a connection. When one executor is reused across different authorization contexts, a later request that omits a sensitive key can send an earlier caller's Authorization or tenant value in its connection_init payload, causing the downstream server to authenticate the later caller as the earlier user. Applications that create a new executor for every request are not affected. This issue is fixed in version 1.1.36 of the GraphQL Tools legacy WebSocket executor package.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @graphql-tools/executor-legacy-ws (npm): fixed in 1.1.36

Ask an AI about this CVE

Show the promptExplain CVE-2026-118665 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118665?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118665?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118665 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ardatan graphql-tools< 9.0.36
@graphql-tools executor-legacy-ws< 1.1.36

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-434m-5hcj-pxf3npm@graphql-tools/executor-legacy-ws<1.1.361.1.36

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as having Moderate impact for Red Hat products because exploitation requires specific design patterns where a legacy WebSocket executor is persistently shared across varying client authentication sessions. Under standard architectures or deployments that instantiate a fresh executor per incoming request, connection parameters remain isolated and credentials are not carried over. While unauthorized callers cannot directly extract stored tokens, unauthenticated queries might receive subscription data authorized under a preceding caller's permissions.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118665.

References

Check your stackJSON