GHSA-9r75-g2cr-3h76: Vercel Workflow Allows Webhook Creation with Predictable User-Specified Tokens
createWebhook() in Vercel Workflow DevKit accepts a user-specified token parameter that serves as the credential for the public webhook endpoint /.well-known/workflow/v1/webhook/{token}. Official documentation recommended predictable token patterns, making it possible for an unauthenticated remote attacker to guess the token and inject arbitrary payloads into the workflow execution context.
Published Mar 6, 2026
Affected packages
workflow
- Ecosystem
- npm
- Affected
- <= 4.1.0-beta.63
- Fixed in
- 4.2.0-beta.64
- Check
npm ls workflow
@workflow/core
- Ecosystem
- npm
- Affected
- <= 4.1.0-beta.63
- Fixed in
- 4.2.0-beta.64
- Check
npm ls @workflow/core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
createWebhook() in Vercel Workflow DevKit accepts a user-specified token parameter that serves as the credential for the public webhook endpoint /.well-known/workflow/v1/webhook/{token}. Official documentation recommended predictable token patterns, making it possible for an unauthenticated remote attacker to guess the token and inject arbitrary payloads into the workflow execution context.
Impact
An attacker who guesses a webhook token can resume the associated workflow with an attacker-controlled HTTP request body, potentially triggering downstream side effects such as API calls, database writes, or deployments.
Fix
- Upgrade to version 4.2.0-beta.64. The fix removes the
tokenoption fromcreateWebhook()so that webhook tokens are always randomly generated by the SDK. - Runs created with versions prior to 4.2.0-beta.64, that are 1) still active (i.e. running), and 2) have open hooks, are still susceptible to this vulnerability. If users suspect the hook tokens are predictable or leaked - consider cancelling those runs and restarting them on the latest patch.
Workarounds
In case a version upgrade is not possible, avoid passing predictable or guessable values to the token parameter of createWebhook(). Instead, users can either
- switch from
createWebhook()tocreateHook()instead and programmatically resume hooks usingresumeHook()instead of the public webhook endpoint, or - use
createWebhook()without passing a user-providedtoken, which uses a non-guessable randomnanoidby default.
Credited to pranaygp, andresriancho, TooTallNate.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
