Spotify bug bounty programs
spotify.com Updated
Spotify runs two public programs: a HackerOne bug bounty paying up to $8,000 and a self-hosted bug bounty.
- Top reward
- $8,000
- HackerOne
- Programs
- 2
- 2 pay cash
- Targets in scope
- 43
- 8 types, deduplicated
- Last change
- None yet
- Tracked since Nov 2026
Where to report
2 programs, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.
Start here
Spotify
HackerOne · Pays the most of the 2 programs: up to $8,000.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
Spotify
HackerOne · Bug bounty |
$8,000 (highest) | $4,000 (highest) | $700 (highest) | $500 (highest) | $8,000 | Partial | – | 38 hours average | Open |
|
Spotify
Self-hosted · Bug bounty |
– | – | – | – | Not published | None | – | – | Open |
-
- Critical
- $8,000 (highest)
- High
- $4,000 (highest)
- Medium
- $700 (highest)
- Low
- $500 (highest)
- Safe harbor
- Partial
- First response
- 38 hours average
-
- Safe harbor
- None
Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
43 targets across all 2 programs, each listed once with the programs that cover it. 8 excluded.
No target matches. Try part of a host name, such as the company name.
Out of scope 8
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
everynoise.com
HackerOne
-
example.com
HackerOne
-
com.soundtrap.studioapp
HackerOne
-
Confidence Domains
HackerOne
-
Findaway
HackerOne
-
Preact
HackerOne
-
Soundtrap
HackerOne
-
The Ringer
HackerOne
Recent changes
Reward and scope changes across every Spotify program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
Recent CVEs
Published vulnerabilities in Spotify products, from the NVD.
-
CVE-2018-1000843 High
Luigi version prior to version 2.8.0; after commit 53b52e12745075a8acc016d33945d9d6a7a6aaeb; after GitHub PR spotify/luigi/pull/1870 contains a Cross ite Request Forgery (CSRF) vulnerability in API endpoint: /api/<method> that can result in Task metadata such as task name, id, parameter, etc. will be leaked to unauthorized users. This attack appear to be exploitable via The victim must visit a spe
-
CVE-2018-1000843 High
Luigi version prior to version 2.8.0; after commit 53b52e12745075a8acc016d33945d9d6a7a6aaeb; after GitHub PR spotify/luigi/pull/1870 contains a Cross ite Request Forgery (CSRF) vulnerability in API endpoint: /api/<method> that can result in Task metadata such as task name, id, parameter, etc. will be leaked to unauthorized users. This attack appear to be exploitable via The victim must visit a spe
-
CVE-2018-1167 High
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Spotify Music Player 1.0.69.336. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of URI handlers. The issue results from the lack of proper validation of a user-supplied
-
CVE-2018-1167 High
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Spotify Music Player 1.0.69.336. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of URI handlers. The issue results from the lack of proper validation of a user-supplied
About this page
This page gathers every public program listed under spotify.com: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.