Insufficient Verification of Data Authenticity Affecting commercial-gitlab-rails-ee-19.1 package, versions <19.1.7-r3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-20650170
- published8 Oct 2026
- disclosed6 Oct 2026
Introduced: 6 Oct 2026
NewCVE-2026-104850 (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.
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Starting in version 1.12.0 and prior to versions 1.31.0 and 2.2.0, the SDK's OAuth client support let the MCP server a client connected to decide which authorization server received the client's OAuth credentials. Stored and pre-provisioned credentials were not bound to the authorization server they belong to. A malicious or compromised MCP server could name its own authorization server in its protected resource metadata. Without any user interaction, the client would send that server the refresh_token and client_secret stored from an earlier sign-in (1.x), or the configured client_secret or signed assertion of a bundled non-interactive provider (1.x and 2.x). Only those applications that use the SDK as an MCP client over HTTP with an authProvider: your own OAuthClientProvider, or the bundled ClientCredentialsProvider, PrivateKeyJwtProvider, StaticPrivateKeyJwtProvider or (2.x) CrossAppAccessProvider and that may connect to an MCP server the owners does not fully trust while holding credentials for a legitimate authorization server are affected. @modelcontextprotocol/sdk 1.31.0 (1.x) and @modelcontextprotocol/client 2.2.0 (2.x) patch the issue. A workaround for those who cannot upgrade is available. 2.0.0 and 2.1.0 already accept expectedIssuer. On 1.x, the only workaround is to connect OAuth-enabled clients only to MCP servers you trust.
References
- https://github.com/modelcontextprotocol/typescript-sdk/commit/edd12e282620ebf770d67316f19cf91d4112a1bd
- https://github.com/modelcontextprotocol/typescript-sdk/pull/2887
- https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/v2.2.0
- https://github.com/modelcontextprotocol/typescript-sdk/security/advisories/GHSA-6qxp-vccf-f47h