Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SQL Injection + Insecure Deserialization leads to Remote Code Execution on https://krisp.aiAnalysed#1842674 | Valid | Deserialization and Object Injection | Critical | 2023-02-22 | – | 119 |
| Authentication bypass for ███ leads to take over any users account.Analysed#1608151 | Valid | Authentication | Critical | 2022-10-31 | – | 48 |
| Authentication CSRF resulting in unauthorized account access on Krisp appAnalysed#1267476 | Valid | Authentication | High | 2022-06-20 | – | 35 |
| Add more seats by paying less via PUT /v2/seats request manipulationAnalysed#1446090 | Valid | Input Validation and Logic | Medium | 2022-06-20 | – | 30 |
| [api.krisp.ai] Race condition on /v2/seats endpoint allows bypassing the original seat limit#1418419 | Valid | Race Conditions | Low | 2022-04-04 | – | 26 |
| Card requirement bypass for business trial#1670304 | Valid | Access Control | Low | 2022-10-21 | – | 22 |
| Force User to Accept Attacker's invite [ Restrict user to create account]#1420070 | Valid | Access Control | Low | 2022-04-25 | – | 10 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (3,187 analysed so far), which can be wrong. Data as of 2026-11-15.