Uh oh!
There was an error while loading. Please reload this page.
chore(deps): upgrade nanoid to ^5.1.16 - #3545
Open
himself65 wants to merge 1 commit into
Open
Conversation
nanoid 5.x < 5.1.16 is affected by CVE-2026-67214 / GHSA-28wg-ghj8-5hjv (non-secure generators can loop indefinitely with negative size). @workflow/core's exact 5.1.6 pin holds every downstream app on the vulnerable version and forces app-level overrides. The caret range also lets nanoid dedupe with other 5.x consumers in the host app (same reasoning as vercel#3498). Workbench apps bumped alongside so the workspace stays on a single copy.
🦋 Changeset detectedLatest commit: f20d576 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
@himself65 is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
VaguelySerious
left a comment
Member
There was a problem hiding this comment.
Workflow SDK doesn't pass user code into nanoid and is thus unaffected by CVE-2026-67214. Will update package in the next update sweep
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
packages/core:nanoid: 5.1.6→^5.1.16(+ the two workbench apps, so the workspace stays on a single copy). Changeset: patch for@workflow/core.Why
>= 4.0.0, < 5.1.16is affected by CVE-2026-67214 / GHSA-28wg-ghj8-5hjv (non-secure generators can loop indefinitely with a negative size). The fixed 5.1.16 has been out since June 24.@workflow/coreis currently the only path through which nanoid 5.x enters a consuming app, so the exact5.1.6pin holds every downstream on the vulnerable version — apps have to carry ananoid@^5.0.0: ^5.1.16override/resolution to close the advisory.Lockfile regenerated with
pnpm@10.20.0 install --lockfile-only— the only movement isnanoid 5.1.6 → 5.1.16.Backport
mainis the 5.0 beta line — could this also be backported to the 4.x release line (like #2653)? That's where consuming apps would actually pick the fix up today.🤖 Generated with Claude Code