security: vulnerability remediation - #127
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.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ca7ccd8. Configure here.
Remediates GHSA-4633-3j49-mh5q (CVE-2026-64647, medium): cache confusion of response bodies for requests containing invalid UTF-8. First patched version on the 16.x line is 16.2.11; 16.2.12 is the current patch. Co-authored-by: Cursor <[email protected]>
ca7ccd8 to
9b223ba
Compare
ulziibay-kernel
left a comment
There was a problem hiding this comment.
Verified the bump against the advisory's first patched version; rebuilt on current main and confirmed the toolchain lock/build is clean. CI green.

Vulnerability Remediation
Fixed
Not Included
Deferred details
Note
Low Risk
Patch-level framework upgrade with no app logic changes; typical post-merge smoke (build/dev) is the main check.
Overview
Bumps Next.js from
^16.2.6to^16.2.12inpackage.jsonand refreshesbun.lockso the resolvednextpackage and matching@next/env/ platform@next/swc-*binaries align on 16.2.12.There are no application or config code changes—only this dependency remediation (per PR context, addressing GHSA-4633-3j49-mh5q on
next).Reviewed by Cursor Bugbot for commit 9b223ba. Bugbot is set up for automated code reviews on this repo. Configure here.