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

Pitch

Vulnerability disclosure program on Self-hosted pitch.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
14
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 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.

This program does not pay cash rewards.

Pays cash
No We do not run a bug bounty program at Pitch that pays out for valid findings.
Response
Within 5 days you will receive an acknowledgment reply email from the security team (usually within 5 working days of your report being received).
Safe harbor
Full Pitch will not seek prosecution of any security researcher who reports, in good faith and in accordance with this policy, any security vulnerability on an in-scope Pitch service.

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

Scope

14 assets you may test, 4 excluded.

Domains 4

  • any website or service served from the pitch.com domain
  • any website or service served from the pitch.io domain
  • pitch.com
  • pitch.io

Source code 4

  • https://github.com/pitch-io/cljest No bounty
  • https://github.com/pitch-io/uix No bounty
  • pitch-io/cljest
  • pitch-io/uix

Android apps 1

  • Pitch mobile applications

Products and areas 5

  • Desktop applications
  • Mobile applications
  • Official integrations
  • Official Pitch integrations
  • Pitch desktop applications
Out of scope (4)
  • Reports indicating that our services do not fully align with "best practice" (e.g. missing security headers or sub-optimal email-related configuration)
  • TLS configuration weaknesses (e.g. "weak" cipher suite support, TLS1.0 support, sweet32, etc)
  • Volumetric vulnerabilities (i.e. simply overwhelming our service with a high volume of requests)
  • Vulnerabilities or weaknesses in third-party services or sub-processors

Rules

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

While testing

  • Avoid privacy violations, degradation of user experience, disruption to production services, and destruction or manipulation of data
  • Only use exploits to the extent necessary to confirm a vulnerability, and stop testing and report the issue immediately if you gain access to any non-public application, any private data, or non-public credentials
  • Add the header Pentest: Researcher to your requests during the tests
  • Avoid aggressive scanners, automated tools, and volumetric attacks
  • Do not send more than 2 requests per second
  • Submit any necessary screenshots, screen records, cURL requests, and reproduction steps to help our security team reproduce the vulnerability
  • Not disclose any vulnerabilities in Pitch systems/services to 3rd parties/the public before the Pitch confirming that those vulnerabilities have been mitigated or rectified
  • We request that all data retrieved during research be securely deleted as soon as it is no longer required and at most, one month after the vulnerability is resolved, whichever occurs soonest

Not accepted

  • Volumetric vulnerabilities (i.e. simply overwhelming our service with a high volume of requests)
  • TLS configuration weaknesses (e.g. "weak" cipher suite support, TLS1.0 support, sweet32, etc)
  • Reports indicating that our services do not fully align with "best practice" (e.g. missing security headers or sub-optimal email-related configuration)
  • Vulnerabilities or weaknesses in third-party services or sub-processors

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 11 Nov 2026. Last checked 5 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.