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

Krisp

Bug bounty on HackerOne krisp.ai

Accepting reports Full safe harbor
Go to program Website
Top reward
$5,000
Top severity paid
Critical
Assets in scope
15
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $5,000
for critical bugs.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $5,000
High $1,000
Medium $500
Low $100
Response
Within 5 days First Response | 5 days
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

15 assets you may test, 6 excluded.

Web 11

  • account.krisp.ai Critical
  • analytics.krisp.ai Critical
  • api.krisp.ai Critical
  • app.krisp.ai Critical
  • download.krisp.ai Critical
  • help-jp.krisp.ai Low No bounty
  • help.krisp.ai Critical No bounty
  • krisp.ai Critical
  • resources.krisp.ai Informational No bounty
  • teams.krisp.ai Critical
  • upld.krisp.ai Critical

Desktop and binaries 2

  • https://download.krisp.ai/mac Critical
  • https://download.krisp.ai/win Critical

Wildcard domains 1

  • *.krisp.ai Critical

Products and areas 1

  • Other Critical
Out of scope (6)
  • metabase.krisp.ai
  • sdk-docs.krisp.ai
  • url5145.krisp.ai
  • voice-ai-newsletter.krisp.ai
  • whatsnew.krisp.ai
  • *dev*.krisp.ai

Rules

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

While testing

  • Please provide detailed reports with reproducible steps.
  • Do not contact with other Krisp users or Krisp employees or interact with them via the platform.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary
  • Do not put a backdoor in the system, not even for the purpose of showing the vulnerability
  • Please use a rate limit of 5 requests per second when using automation.
  • Please test on the staging environment, then you must verify on the production environment
  • When assessing the backend, please run your scanners only on the staging environment

Not accepted

  • Vulnerabilities in 3rd parties
  • Zero-day vulnerabilities that have had an official patch for less than 1 month
  • Bypassing free minutes limitation via changing frontend applications' logic, integrity
  • Ability to reverse-engineer an application, lack of binary protection
  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user's device
  • Previously known vulnerable libraries without a working Proof of Concept
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability
  • Missing best practices in SSL/TLS configuration
  • Network-level Denial of Service (DoS/DDoS) vulnerabilities
  • Content spoofing and text injection issues without showing an attack vector
  • Rate limiting or bruteforce issues on non-authentication and non-sensitive endpoints
  • Missing best practices in Content Security Policy
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Missing DNSSEC
  • Vulnerabilities only affecting users of outdated or unpatched browsers
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers
  • Tabnabbing
  • Issues that require unlikely user interaction
  • Issues that require edit/admin permissions
  • Issues that require local account access (MacOS, Windows, Android/iOS)

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour 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.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Krisp looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Krisp will make a best effort to meet the following SLAs for hackers participating in our program:

Type of Response SLA in business days
First Response 5 days
Time to Triage 10 days
Time to Bounty 14 days
Time to Resolution depends on severity and complexity

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

  • As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
  • Do not post vulnerabilities without our consent, this includes but is not limited to: posting your proof of concept on for example, Twitter, YouTube, Vimeo, etc.
  • Follow HackerOne's disclosure guidelines.

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

  • Do not contact with other Krisp users or Krisp employees or interact with them via the platform.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • In case that a reported vulnerability was already known to the company from our own tests, it will be flagged as a duplicate.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability.
  • Do not put a backdoor in the system, not even for the purpose of showing the vulnerability as inserting a backdoor will cause even more damage to the safety of our systems.
  • Please use a rate limit of 5 requests per second when using automation.

Test plan

Main scope

Secondary scope

  • https://krisp.ai,
  • *.krisp.ai,
  • Any resource that is verified that belongs to us (verify with [email protected]),
  • Leaks that have security impact (github, pastbin, etc),
  • Misconfigurations in 3rd parties such as whatsnew.krisp.ai, help.krisp.ai.

Rewards

All amounts are for reference purposes only. Reward applicability and reward amount may depend on problem severity, novelty, exploitation probability, environmental and other factors. Reward decision is made by Krisp security team for each report individually.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Vulnerabilities in 3rd parties (although we are eager to hear them and address those to the proper parties),
  • Zero-day vulnerabilities that have had an official patch for less than 1 month may be awarded on a case by case basis,
  • Bypassing free minutes limitation via changing frontend applications' logic, integrity,
  • Ability to reverse-engineer an application, lack of binary protection,
  • Clickjacking on pages with no sensitive actions,
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions (for example logout CSRFs),
  • Reports of missed protection mechanism / best current practice (e.g. no CSRF token, framing/clickjacking protection, reflecting Origin) without demonstration of real security impact for user or system,
  • Attacks requiring MITM or physical access to a user's device,
  • Previously known vulnerable libraries without a working Proof of Concept,
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability,
  • Missing best practices in SSL/TLS configuration,
  • Network-level Denial of Service (DoS/DDoS) vulnerabilities,
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS,
  • Rate limiting or bruteforce issues on non-authentication and non-sensitive endpoints ,
  • Missing best practices in Content Security Policy,
  • Missing HttpOnly or Secure flags on cookies,
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.),
  • Missing DNSSEC,
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version],
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing,
  • Issues that require unlikely user interaction,
  • Issues that require edit/admin permissions will most likely be rated as low or closed.
  • Issues that require local account access (MacOS, Windows, Android/iOS) will be rated as low in most of the cases.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Krisp and our users safe!