Homepage

Improper Certificate Validation Affecting commercial-gitlab-rails-ee-19.1 package, versions <19.1.7-r3

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.27% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-COMMERCIALGITLABRAILSEE191-20651615
  • published8 Oct 2026
  • disclosed1 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 1 Oct 2026

NewCVE-2026-103921  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Chainguard commercial-gitlab-rails-ee-19.1 to version 19.1.7-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream commercial-gitlab-rails-ee-19.1 package and not the commercial-gitlab-rails-ee-19.1 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.