Repository navigation
security: vulnerability remediation - #252
kernel-internal[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
35ddde7 to
4609629
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4609629. Configure here.
| }, | ||
| "devDependencies": { | ||
| "@modelcontextprotocol/sdk": "1.26.0", | ||
| "@modelcontextprotocol/sdk": "1.32.0", |
There was a problem hiding this comment.
Claimed Next.js upgrade not applied
Medium Severity
The PR marks GHSA-39w2-rjm5-chcv as confirmed by moving next from 16.3.6 to 16.3.8, but next remains resolved at 16.3.6. The commit instead bumps test-only @modelcontextprotocol/sdk, so the Next.js development MCP origin check stays unpatched.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 4609629. Configure here.


Vulnerability Remediation
Fixed
Not Included
Deferred details
Note
Low Risk
Dev-only dependency and lockfile changes with no runtime code edits; main risk is tooling or peer-resolution behavior around MCP SDK 1.32.0.
Overview
This PR bumps the devDependency
@modelcontextprotocol/sdkfrom 1.26.0 to 1.32.0 inpackage.jsonand refreshesbun.lockaccordingly. There are no application or config source changes—only the manifest and lockfile.The lockfile update also widens the resolved SDK dependency on
@hono/node-server(now^1.19.9 || ^2.0.5) and drops the previous nested@modelcontextprotocol/sdk/zod→zod@3.25.76entry, so dependency resolution for the SDK subtree is slightly different after the upgrade.Reviewed by Cursor Bugbot for commit 4609629. Bugbot is set up for automated code reviews on this repo. Configure here.