fix(security): upgrade @modelcontextprotocol/sdk to 1.26.0 to resolve data-leak advisory#43
Open
shwetanaren wants to merge 1 commit intoexcalidraw:mainfrom
Open
Conversation
|
@shwetanaren is attempting to deploy a commit to the Excalidraw Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
Hi team |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR description
This PR upgrades @modelcontextprotocol/sdk from 1.25.2 to 1.26.0 to address the high-severity advisory
GHSA-345p-7cg4-v4c7 (cross-client data leak via shared transport/server instance reuse).
Why
pnpm audit reported a High vulnerability affecting the current version.
The issue is resolved in @modelcontextprotocol/sdk >= 1.26.0.
Changes
Bumped SDK version in package.json
Updated pnpm-lock.yaml
Verification
pnpm install
pnpm audit --audit-level high → no High vulnerabilities
pnpm run build → successful
No functional code changes; dependency security update only.