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

Tiger Data

Vulnerability disclosure program on Self-hosted tigerdata.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
0
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.
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 Tiger Data does not currently run a bug bounty program. While we greatly appreciate security researchers who help keep our systems secure, we do not offer monetary rewards for vulnerability reports.
Safe harbor
Full We consider activities conducted in accordance with this policy to be authorized conduct and will not pursue civil action or initiate a complaint to law enforcement.
Hall of fame
Yes Inclusion in a security researchers hall of fame or recognition page (if you choose to be credited)

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

Scope

0 assets you may test, 29 excluded.

Self-hosted does not list the scope of this program publicly. Check its policy.

Out of scope (29)
  • Autocomplete or save password functionality being available
  • Clickjacking/UI redressing with no practical security impact
  • Clickjacking with no practical security impact
  • Descriptive error messages (e.g. stacktraces, application or server errors)
  • Descriptive error messages such as stack traces
  • DoS/DDoS or any other testing that would impact the operation of our systems
  • Functional, UI and UX bugs, and spelling mistakes
  • Functional, UI, and UX bugs and spelling mistakes
  • Internal IP disclosure
  • Lack of rate limit on non-sensitive endpoints and/or brute force attacks
  • Lack of the X-FRAME-OPTIONS header
  • Login or Forgot Password page brute force and account lockout not enforced
  • Logout Cross-Site Request Forgery (logout CSRF)
  • Logout CSRF
  • Missing cookie flags on non-sensitive cookies
  • Missing HTTP security headers
  • Open ports that do not lead directly to a vulnerability
  • OPTIONS/TRACE HTTP method enabled
  • OPTIONS/TRACE HTTP methods enabled
  • Presence/absence of SPF/DMARC records
  • Presence of application or web browser 'autocomplete' or 'save password' functionality
  • Presence or absence of SPF/DMARC records
  • Self XSS
  • SSL/TLS best practices
  • Testing third-party applications or services
  • The Anti-MIME-Sniffing header X-Content-Type-Options
  • Third-party applications or services
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
  • Vulnerabilities that require extensive social engineering

Rules

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

While testing

  • Make a good-faith effort to avoid privacy violations, data destruction, and service disruption
  • Only access data that is necessary to demonstrate the existence of a vulnerability
  • Promptly report vulnerabilities through the channels described below
  • Do not publicly disclose vulnerabilities prior to remediation or without our written consent
  • Testing should not disrupt any Tiger Data services or access data beyond your own test accounts
  • Do not perform any testing that could impact the availability or integrity of our systems or customer data
  • Only test against systems you own or have explicit permission to test

Not accepted

  • SSL/TLS best practices
  • DoS/DDoS or any other testing that would impact the operation of our systems
  • Lack of rate limit on non-sensitive endpoints and/or brute force attacks
  • Open ports that do not lead directly to a vulnerability
  • Missing HTTP security headers
  • Descriptive error messages (e.g. stacktraces, application or server errors)
  • Missing cookie flags on non-sensitive cookies
  • Logout Cross-Site Request Forgery (logout CSRF)
  • OPTIONS/TRACE HTTP method enabled
  • Lack of the X-FRAME-OPTIONS header
  • The Anti-MIME-Sniffing header X-Content-Type-Options
  • Presence/absence of SPF/DMARC records
  • Internal IP disclosure
  • Clickjacking/UI redressing with no practical security impact
  • Presence of application or web browser 'autocomplete' or 'save password' functionality
  • Login or Forgot Password page brute force and account lockout not enforced
  • Self XSS
  • Functional, UI, and UX bugs and spelling mistakes
  • Vulnerabilities that require extensive social engineering
  • Testing third-party applications or services
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms

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.