mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 08:25:34 +02:00
[PR #476] [MERGED] fix: pin Rollup to patched version for CVE-2026-27606 #599
Labels
No labels
enhancement
enhancement
good first issue
help wanted
nextjs-tracking
nextjs-tracking
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vinext#599
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/cloudflare/vinext/pull/476
Author: @Divkix
Created: 3/11/2026
Status: ✅ Merged
Merged: 3/11/2026
Merged by: @james-elicx
Base:
main← Head:fix/rollup-cve-2026-27606📝 Commits (1)
e54fa55fix: pin rollup to patched version📊 Changes
2 files changed (+123 additions, -117 deletions)
View changed files
📝
package.json(+3 -0)📝
pnpm-lock.yaml(+120 -117)📄 Description
Closes #475.
Summary
This pins the workspace Rollup resolution to a patched version via a pnpm override and refreshes the lockfile.
Why
The repository was resolving
rollup@4.57.1, which is affected byCVE-2026-27606/GHSA-mw96-cpmx-2vgc.vite@7.3.1accepts newer Rollup versions, so4.59.0is a semver-compatible fix.Changes
pnpm.overrides.rollupentrypnpm-lock.yamlto resolverollup@4.59.0Validation
pnpm why rolluppnpm exec vite --versionpnpm run fmt:checkNotes
This looks like a build-time/tooling exposure rather than a vinext runtime server issue, but the repo should still stop resolving the vulnerable version.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.