Vercel bug bounty programs
workflow-sdk.dev Updated
Vercel runs one public program: a Sorona bug bounty paying up to $6,000.
- Top reward
- $6,000
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 9
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program Vercel runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
Vercel Workflow
Sorona · Bug bounty |
– | $6,000 | $1,250 | $625 | $6,000 | Partial | – | 24 hours promised | Open |
-
- Critical
- –
- High
- $6,000
- Medium
- $1,250
- Low
- $625
- Safe harbor
- Partial
- First response
- 24 hours promised
Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
9 targets. 8 excluded.
-
https://workflow-sdk.dev
Web
-
Durable state, meaning the journal the runtime writes, its serialization format, and the replay that reconstructs a run from it
Products and areas
-
Event handling, plus the hooks, sleeps, timers and webhooks a workflow can suspend on
Products and areas
-
Step completion handling, covering acknowledgement, idempotency and whatever proves a completion genuine
Products and areas
-
The HTTP entry points the framework mounts to receive events, callbacks and completions, along with the authentication on them
Products and areas
-
The published npm package and its supply chain, which the policy names in scope
Products and areas
-
The tenant and workflow-identity boundary that keeps one party's runs, state and triggers away from another's
Products and areas
-
The vercel/workflow repository itself, listed under Tier 1 (High Priority) as a source-code asset that is bounty-eligible up to critical severity, with the asset instruction repeating the tiering
Products and areas
-
The workflow runtime: how a step is scheduled, dispatched, retried and resumed after a crash
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 8
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Cloud-provider and deployment-specific issues, which belong to Vercel's main platform program rather than the open-source one
-
Dependency CVE reports without a demonstrated chain through Workflow in context
-
Issues that only reproduce in a canary or release-candidate build already superseded by a stable release
-
Issues that require the attacker to already hold privileged access to the workflow or its host
-
Reports without the mandatory working proof-of-concept zip demonstrating the chain on a production-equivalent deployment
-
Static-analysis or scanner output submitted without a working exploit chain
-
Unverified findings produced by AI or LLM tooling
-
Vulnerabilities that arise from a developer's own workflow design, such as a step they wrote with no authorization check
Recent changes
Reward and scope changes across every Vercel program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
About this page
This page gathers every public program listed under workflow-sdk.dev: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.