p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in @graphql-tools/executor-legacy-ws

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für @graphql-tools/executor-legacy-ws: 3. Davon im KEV-Katalog: 0.

RSS ↗ JSON ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3

  1. CVE-2026-118666

    Mittel · CVSS 6EPSS 0,34%Öffentlicher ExploitKorrektur verfügbar

    GraphQL Tools: Shared legacy executor routes one subscription's results to a different caller

    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 reuses one WebSocket and replaces its single websocket.onmessage handler whenever a new overlapping subscription starts. The handler delivers LEGACY_WS.DATA frames to the newest observer without comparing data.id with the subscription operation id, so a caller using the same executor can receive another user's authorized subscription payload while the earlier caller's stream is starved. This issue is fixed in ver

    @graphql-tools/executor-legacy-wsNode.js
    • Auf 1.1.36 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  2. CVE-2026-118665

    Hoch · CVSS 8.2EPSS 0,39%Öffentlicher ExploitKorrektur verfügbar

    GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications

    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 e

    @graphql-tools/executor-legacy-wsNode.js
    • Auf 1.1.36 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  3. CVE-2026-103921

    Hoch · CVSS 7.4EPSS 0,27%Korrektur verfügbar

    GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor

    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 vali

    @graphql-tools/executor-legacy-wsNode.js
    • Auf 1.1.35 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →