security: vulnerability remediation

[kernel-internal]

Vulnerability Remediation

This PR was generated by the Socket-centric vulnerability remediation workflow. Review the planned dependency changes and confirmation evidence before merging.

Fixed

CVE/GHSA	Package	Ecosystem	Old Version	New Version	Manifest	Confirmation
GHSA-267c-6grr-h53f	next	None	16.0.10	16.2.6		confirmed

Not Included

• Deferred by batch limit: 50 advisories. They will be considered by future runs.
• Other deferred scanner findings: 0.
• Unconfirmed attempted fixes: 0.

---

Note

Low Risk
Patch/minor framework bump with no app diff; main residual risk is standard post-upgrade smoke (build, dev server, MCP routes).

Overview
Bumps Next.js from 16.0.10 to 16.2.6 in package.json and refreshes bun.lock to address GHSA-267c-6grr-h53f. There are no application source changes—only the framework and its platform packages (@next/env, @next/swc-*) move to 16.2.6.

The lockfile also picks up Next’s new transitive dependency baseline-browser-mapping and a minor optional sharp bump (^0.34.5). Existing peers such as @clerk/nextjs already allow Next 16.

^{Reviewed by Cursor Bugbot for commit 484563e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mcp	Ready	Preview, Comment	Jun 3, 2026 4:39am

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​16.0.10 ⏵ 16.2.6	+5	+75	+1

View full report

[firetiger-agent]

Created a monitoring plan for this PR.

What this PR does: Patches the MCP server's Next.js framework to version 16.2.6 to remediate known security vulnerabilities. No user-facing feature changes.

Intended effect:

• Vercel build status: baseline all recent Production deploys SUCCESS; confirmed if this SHA also reaches success in Preview and Production without errors.
• MCP endpoint availability: baseline no prior incidents; confirmed if https://mcp.onkernel.com/mcp continues to serve tool definitions and handle requests after deploy.

Risks:

• Vercel build failure — a Next.js 16.0→16.2 incompatibility with the existing codebase or a dependency could break the build; alert if Vercel deployment status reaches failure or error for this SHA.
• MCP route runtime error — if Next.js 16.2.6 introduces a breaking change affecting the /mcp API handler, clients would receive 5xx responses; alert on any sustained MCP endpoint 500s post-deploy.
• Indirect API regression — MCP tool calls proxy to the main Kernel API; alert if Railway HTTP 5xx rate rises above 0.1% for 2+ consecutive hours (baseline 0.002–0.029%).

Status updates will be posted automatically on this PR as monitoring progresses.

View monitor

[ulziibay-kernel]

lgtm

[firetiger-agent]

Next.js security upgrade confirmed at 2m post-deploy across Production.

Signals:

• Vercel Production deployment: success (SHA 144da94 at 15:48:30Z)
• Railway HTTP 5xx rate: 0.0207% (13/62,949) — within baseline 0.002–0.029%

Risks watched:

• Vercel build failure
• MCP endpoint 500s

Monitoring window open for ~72h. No issues detected.

View monitor

[firetiger-agent]

No issue detected after 72h across 1 environment.

Per-environment outcomes:

• Production: intended effect confirmed, no regressions.

Evidence:

• Vercel Production deployment: success (2026-06-03T15:48:28Z)
• Railway HTTP 5xx rate: 0.000–0.029% post-deploy (within baseline 0.002–0.029%)
• Jun 3 21:00–22:00Z spike (0.538%/0.378%): pre-existing evening pattern, not deploy-correlated (recurred Jun 5 without new deploy; pre-deploy Jun 2 baseline already elevated)

View monitor