Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
26
Disclosed reports
16
Subdomains
1,259
Vendor on CyberSIXT
Vercel (80 CVEs, 0 exploited)

Most upvoted reports16

All reports
Most upvoted reports of Vercel
ReportWeaknessDisclosedBountyVotes
Revoked deployment collaborator regains access to private comments after active collaborator interaction#3852102Input Validation and Logic2026-10-29$1,02655
Open redirect vuln on login#608031Open Redirect––45
through %09 Character the attacker is able to steal Github Token [ Account Takeover ]#763058Open Redirect––44
Gitlab Oauth Misconfiguration Lead To Account Takeover#541701No weakness recorded––39
Open Redirect on Gitllab Oauth leading to Acount Takeover#677617Open Redirect––34
CSRF On Connect Account With Github Lead To Account Takeover#542047Cross-Site Request Forgery––29
Stored XSS on Zeit.co user profile#541737Cross-site Scripting––21
Stored Cross-site scripting#541710Cross-site Scripting––13
User personal data disclosure via API#630235Information Disclosure––12
[Fix Bypass #541631] Open redirect on Signup#541948Open Redirect––9

Subdomains1,259

Subdomains of Vercel
NameScopeFirst seen
ghes-test.now.systemstestNot in the scope2026-11-14
vue.test.vercel.comtestIn scope2026-11-14
test000002.vercel.comtestIn scope2026-11-14
lb.vue.test.vercel.comtestIn scope2026-11-14
test.vertex.vercel.comtestIn scope2026-11-14
test0000001.vercel.comtestIn scope2026-11-14
annonce.test.vercel.comtestIn scope2026-11-14
sbx.beincomm.vercel.comtestIn scope2026-11-14
dusstech.test.vercel.comtestIn scope2026-11-14
test.test0001.vercel.comtestIn scope2026-11-14
test.test0002.vercel.comtestIn scope2026-11-14
coba-next.test.vercel.comtestIn scope2026-11-14
pharma.testing.vercel.comtestIn scope2026-11-14
www.test.dusstech.vercel.comtestIn scope2026-11-14
dusstech.test.vercel.vercel.comtestIn scope2026-11-14
testing-this-hello.testing01001.vercel.comtestIn scope2026-11-14
vercel-live-git-front-test.vercel.shgit, testNot in the scope2026-11-14
api-git-services-turbo-test.vercel.shapi, git, testNot in the scope2026-11-14
binshtok-cowan-test-pwjs2ggdx.vercel.shtestNot in the scope2026-11-14
feedback-test-git-hobby-limits.vercel.shgit, testNot in the scope2026-11-14
wildcard.vercel-live-git-front-test.vercel.shgit, testNot in the scope2026-11-14
next-site-git-padmaia-testing-admin-check.vercel.shadmin, git, testNot in the scope2026-11-14
pyra-docs-git-padmaia-testing-admin-check.vercel.shadmin, git, testNot in the scope2026-11-14
vercel-site-git-padmaia-testing-admin-check.vercel.shadmin, git, testNot in the scope2026-11-14
feedback-test-main-injector-git-hobby-limits.vercel.shgit, testNot in the scope2026-11-14
analytics-script-git-padmaia-testing-admin-check.vercel.shadmin, git, testNot in the scope2026-11-14
demo.zeit.shtestNot in the scope2026-11-14
test.zeit.shtestNot in the scope2026-11-14
gws-qa.zeit.shtestNot in the scope2026-11-14
gws-uat.zeit.shtestNot in the scope2026-11-14
testing.zeit.shtestNot in the scope2026-11-14
cim-api-qa.zeit.shapi, testNot in the scope2026-11-14
akamai-test.zeit.shtestNot in the scope2026-11-14
cim-api-uat.zeit.shapi, testNot in the scope2026-11-14
pingdom-tests.zeit.shtestNot in the scope2026-11-14
gws-api-sandbox.zeit.shapi, testNot in the scope2026-11-14
searchportal-qa.zeit.shtestNot in the scope2026-11-14
test-deployment.zeit.shtestNot in the scope2026-11-14
assertible-tests.zeit.shtestNot in the scope2026-11-14
akamai-test-origin.zeit.shtestNot in the scope2026-11-14
cim-data-quality-qa.zeit.shtestNot in the scope2026-11-14
gcom-product-find-qa.zeit.shtestNot in the scope2026-11-14
logs-every-second.test.zeit.shmonitoring, testNot in the scope2026-11-14
wildcard.pingdom-tests.zeit.shtestNot in the scope2026-11-14
wildcard.assertible-tests.zeit.shtestNot in the scope2026-11-14
gws-rds-external-readonly-uat.zeit.shtestNot in the scope2026-11-14

378 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-14.

Updated AboutDevelopersSign in