mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 08:25:34 +02:00
[GH-ISSUE #475] Pin Rollup to >=4.59.0 for CVE-2026-27606 #106
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#106
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?
Originally created by @Divkix on GitHub (Mar 11, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/475
Summary
The repo currently resolves
rollup@4.57.1in the workspace lockfile, which is affected byCVE-2026-27606/GHSA-mw96-cpmx-2vgc.GitHub Advisory: https://github.com/advisories/GHSA-mw96-cpmx-2vgc
OSV: https://osv.dev/vulnerability/GHSA-mw96-cpmx-2vgc
Current state
pnpm-lock.yamlresolvesrollup@4.57.1vite@7.3.1and@mdx-js/rolluprollup@4.59.0Impact
This appears to be a build-time/tooling exposure rather than a vinext runtime server issue, but the repository should still stop resolving the vulnerable Rollup version.
Proposed fix
Add a pnpm override for
rollupand refresh the lockfile so the workspace resolves4.59.0or newer.Validation
vite@7.3.1accepts newer Rollup versions (^4.43.0), so4.59.0is semver-compatible.