Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Capgo

Bug bounty on security.txt capgo.app

Accepting reports Full safe harbor security.txt mentions bounty
Go to program Website
Top reward
Not published
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report through their form
github.com/Cap-go/capgo.app/security/advisories/new
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 7 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes We accept and review security reports for Capgo plugins, but paid bounties for plugin code are limited to @capgo/capacitor-updater.
Response
Within 7 days We will respond to your report within 7 business days with our evaluation of the report and an expected resolution date.
Safe harbor
Full If you have followed the instructions above, we will not take any legal action against you in regard to the report.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test, 16 excluded.

Domains 1

  • capgo.app

Source code 1

  • @capgo/capacitor-updater
Out of scope (16)
  • Access to Capgo bundle files or proof that bundle files can be downloaded.
  • Any activity that could lead to the disruption of our service (DoS).
  • Attacks requiring MITM or physical access to a user's device.
  • Attacks requiring social engineering.
  • Clickjacking on pages with no sensitive actions.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
  • Deadlinks
  • Email spoofing
  • Lack of Secure or HTTP only flag on non-sensitive cookies
  • Missing DNSSEC, CAA, CSP headers
  • SSRF or DNS spoofing reports against webhooks or website preview.
  • Unauthenticated Capgo plugin/API endpoints that are intentionally public by design
  • Unauthenticated/logout/login CSRF.
  • Uploader or UI incorrectly labeling encryption for bundles served via external_url
  • User enumeration
  • User-owned application code or project configuration that Capgo does not own, ship, or control

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Capgo's policy. "We" in these lines means the program, not this site.

While testing

  • Do not run automated scanners on other customer projects.
  • If you wish to run an automated scanner, notify us at [email protected] and only run it on your own Capgo project.
  • Do NOT attack projects of other customers.
  • Do not take advantage of the vulnerability or problem you have discovered
  • Do provide sufficient information to reproduce the problem
  • do not reveal the problem to others until we have researched, addressed and informed our affected customers.
  • you should share a draft with us for review and approval at least 30 days prior to the publication date.

Not accepted

  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Attacks requiring social engineering.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
  • Email spoofing
  • Missing DNSSEC, CAA, CSP headers
  • Lack of Secure or HTTP only flag on non-sensitive cookies
  • Deadlinks
  • User enumeration
  • SSRF or DNS spoofing reports against webhooks or website preview.
  • User-owned application code or project configuration that Capgo does not own, ship, or control
  • Access to Capgo bundle files or proof that bundle files can be downloaded.
  • Unauthenticated Capgo plugin/API endpoints that are intentionally public by design
  • Uploader or UI incorrectly labeling encryption for bundles served via external_url

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 12 Nov 2026. Last checked 3 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.