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.
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.
token option from createWebhook() so that webhook tokens are always randomly generated by the SDK.In case a version upgrade is not possible, avoid passing predictable or guessable values to the token parameter of createWebhook(). Instead, users can either
createWebhook() to createHook() instead and programmatically resume hooks using resumeHook() instead of the public webhook endpoint, orcreateWebhook() without passing a user-provided token, which uses a non-guessable random nanoid by default.{
"github_reviewed": true,
"cwe_ids": [
"CWE-287"
],
"nvd_published_at": null,
"github_reviewed_at": "2026-03-06T18:45:02Z",
"severity": "MODERATE"
}