Skip to content

chore(deps): upgrade nanoid to ^5.1.16 - #3545

Open
himself65 wants to merge 1 commit into
vercel:mainfrom
himself65:chore/bump-nanoid-5.1.16
Open

chore(deps): upgrade nanoid to ^5.1.16#3545
himself65 wants to merge 1 commit into
vercel:mainfrom
himself65:chore/bump-nanoid-5.1.16

Conversation

@himself65

Copy link
Copy Markdown

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

  • nanoid >= 4.0.0, < 5.1.16 is 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/core is currently the only path through which nanoid 5.x enters a consuming app, so the exact 5.1.6 pin holds every downstream on the vulnerable version — apps have to carry a nanoid@^5.0.0: ^5.1.16 override/resolution to close the advisory.
  • Caret rather than a new exact pin, for the same reason as [deps] Dedupe zod and undici by publishing caret ranges #3498: an exact pin can only ever match one version, so any other 5.x consumer in the host app gets a second copy.

Lockfile regenerated with pnpm@10.20.0 install --lockfile-only — the only movement is nanoid 5.1.6 → 5.1.16.

Backport

main is 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

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.
@himself65
himself65 requested a review from a team as a code owner August 14, 2026 02:50
@changeset-bot

changeset-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f20d576

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages
Name Type
@workflow/core Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/vitest Patch
@workflow/web-shared Patch
@workflow/web Patch
workflow Patch
@workflow/world-testing Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/nuxt Patch

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

@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown
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.

@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​nanoid@​5.1.161001007995100

View full report

@VaguelySerious VaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants