- Top reward
- €1,000
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to €1,000
- for critical bugs, from €100.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
Rewards
What the company's own policy page says it pays.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€1,000 |
| High |
|
€500 |
| Low |
|
€100 |
- Top reward
-
€1,000
| Critical | 1000 |
- Lowest reward
-
€100
| Low | 100 |
- Safe harbor
-
Partial
We'll assume good faith in all reports. However, if in doubt, ask us before engaging in any specific action you think might have serious consequences for our users or systems.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Domains 1
- cabify.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Cabify's policy. "We" in these lines means the program, not this site.
While testing
-
We'll assume good faith in all reports. However, if in doubt, ask us before engaging in any specific action you think might have serious consequences for our users or systems.
-
We expect you to respect our users' privacy and data. Please do not access, modify, or delete data that does not belong to you. If you encounter sensitive data while researching, please stop and report it immediately.
-
We do not respond to introductory or exploratory emails. Our bug bounty program is public, and this document serves as its official policy.
Not accepted
-
Any vulnerabilities requiring significant and unlikely interactions
-
HTTP 404 codes/pages or other HTTP non-200 codes/pages
-
Host Header Attacks
-
Fingerprinting / banner disclosure on public services
-
Lack of Secure/HTTPOnly flags on non-sensitive Cookies
-
Mixed Content Scripting
-
Not performing rate limiting on non-critical endpoints
-
OPTIONS HTTP method enabled
-
SPF, DKIM, or DMARC settings
-
SSL/TLS protocol scan reports
-
Speculative reports about theoretical vulnerabilities without a PoC
-
Theoretical sub-domain takeovers with no supporting evidence
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.