@workflow/web 5.0.7 server build inlines brace-expansion 5.0.6 (via @vercel/queue → minimatch)

Open
#5,210 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

The vulnerable copy is brace-expansion 5.0.6, pulled in through @vercel/queue and minimatch 10.2.5, and it ends up inlined in the @workflow/web build output build/server/assets/app-CGNn2sgH.js. Start in pnpm-lock.yaml and check whether a root override can force brace-expansion to 5.0.12 or later. Done means the lockfile resolves the fixed version and a rebuilt bundle no longer contains the old expand_ logic.

Written by the indexing model from the issue text.

Description

While scanning published npm packages for bundled third-party code we found that @workflow/[email protected] (npm latest) inlines brace-expansion 5.0.6 in build/server/assets/app-CGNn2sgH.js (:140336 onward). It comes in through the bundled @vercel/queue client → minimatch 10.2.5, which the vercel/workflow pnpm-lock.yaml on main still resolves to [email protected].

  • CVE-2026-13149 (GHSA-3jxr-9vmj-r5cp): DoS via exponential-time expansion of consecutive non-expanding {} groups (fixed 5.0.7)
  • CVE-2026-14257 (GHSA-mh99-v99m-4gvg): DoS via unbounded expansion length (fixed 5.0.8)
  • CVE-2026-69152 (GHSA-rgw5-rvv9-x895): DoS via unbounded intermediate arrays (fixed 5.0.9)
  • CVE-2026-102276 (GHSA-6j4f-fj2g-mc7p): DoS via uncontrolled recursion in parseCommaParts (fixed 5.0.10)
  • CVE-2026-102278 (GHSA-qhr7-859c-m2p7): DoS via uncontrolled recursion on nested brace groups (fixed 5.0.11)
  • CVE-2026-102277 (GHSA-q2hr-2g5m-vwhr): quadratic-time expansion of the {a},b} rewrite (fixed 5.0.12)

@workflow/web does not declare brace-expansion or minimatch, so npm audit and SCA tools cannot flag this copy for you or your users.

We did not find a way for it to lead to an exploit in this package.

Because the copy ships where dependency audits cannot see it, it is easy to miss. We would suggest updating it when convenient, and sooner if untrusted input can reach it in your setup.

Suggested fix: update the lockfile (or add an override) so minimatch resolves brace-expansion >= 5.0.12, then rebuild @workflow/web.

Reproduction

Checked against the published tarball on 2026-11-03 (npm latest):

npm pack @workflow/[email protected] && tar xzf workflow-web-5.0.7.tgz
grep -n 'const EXPANSION_MAX = ' package/build/server/assets/app-CGNn2sgH.js
grep -n 'return expand_(str, max2, true)' package/build/server/assets/app-CGNn2sgH.js
grep -c 'EXPANSION_MAX_LENGTH' package/build/server/assets/app-CGNn2sgH.js

Output:

140336:const EXPANSION_MAX = 1e5;
140408:        return expand_(str, max2, true);
0

The inlined expand_ still restarts on the {a},b} rewrite by recursing (:140408), which 5.0.7 turned into a loop, and EXPANSION_MAX_LENGTH (added in 5.0.8) is absent.

Dominant language
TypeScript
Stars
2.5k
Forks
401
Avg merge
1d 21h
Merged PRs (30d)
201

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/workflow

All issues in vercel/workflow

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.