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

ConfigCat

Bug bounty on security.txt configcat.com

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

At a glance

What to know before you start testing.

Pays up to $2,000
top reward, from $5.
Report by email
https://configcat.com/bounty/
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 14 days
As the policy promises.
Paid by PayPal
Proof of identity needed to get paid.
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.

Top reward
$2,000 Catastrophic impact. │ $500 │ $2000
Lowest reward
$5 Unnoticed by the customers, a few hours of work for our team to resolve the situation. │ $5 │ $50
Response
Within 14 days This might take several days, in some cases up to 2 weeks.
Safe harbor
Full We will not take legal action against you if you have acted in good faith.

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

Scope

7 assets you may test, 6 excluded.

Domains 6

  • api.configcat.com
  • app.configcat.com
  • cdn-eu.configcat.com
  • cdn-global.configcat.com
  • configcat.com
  • dashboard-api.configcat.com

Products and areas 1

  • Social media accounts run by ConfigCat
Out of scope (6)
  • status.configcat.com
  • our support channels
  • Social media accounts run by ConfigCat.
  • Status pages (e.g. status.configcat.com).
  • The Contact Us page.
  • The DEMO booking functionality.

Rules

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

While testing

  • Do NOT perform load tests, stress tests or DoS attacks.
  • Do NOT test our support channels.
  • Report issues ONLY to us.
  • Always send proof of the issue. A video is best.
  • You must not disclose a vulnerability without our formal consent.
  • You must not access data for accounts that you do not own.
  • You must not conduct non-technical attacks such as phishing, social engineering or physical attacks against our employees, customers or infrastructure.
  • You must not exploit a security issue you discover for any reason.
  • You must give us reasonable time to investigate, confirm and mitigate an issue you report to us before you make public any information about any vulnerabilities from your report.

Not accepted

  • Already known vulnerabilities.
  • Bugs related to browser extensions are out of scope.
  • Source code disclosures, as most of our code is open source.
  • CSRF for non-significant actions (logout, etc.)
  • Clickjacking attacks without a documented series of clicks that produce a vulnerability.
  • Spam.
  • Attacks that require social engineering (phishing).
  • Content injection, such as reflected text or HTML tags.
  • Missing HTTP headers, except as where their absence fails to mitigate an existing attack.
  • Authentication bypasses that require access to software/hardware tokens.
  • Bugs that are in content/services not owned by ConfigCat.
  • Brute forcing of intended functionality.
  • Leaking version or debugging information such as stack traces, path disclosure, or directory listings.
  • Speculative reports or reports without enough information to confirm an issue.
  • Reports recommending best practices without demonstrable proof of an actual issue.
  • Non-technical vulnerabilities such as DDoS, phishing, breaking and entering are not qualified for our bounty program.

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 2 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.