- Top reward
- Not published
- Top severity paid
- Critical
- Assets in scope
- 4
- Public CVEs
- 2
- Last change
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report on HackerOne
- Submit through the program page.
Rewards
What HackerOne lists as the payout for each severity.
HackerOne does not publish a reward table for this program.
Scope
4 assets you may test.
Web 2
- dashboard.algolia.com Critical
- www.algolia.com Critical
Wildcard domains 2
- *.algolia.net No bounty
- *.algolianet.com No bounty
Changes
Tracked since 12 Nov 2026. Last checked 1 hour ago.
-
Paused
Paused. Not accepting reports right now.
-
Back
Open for reports again.
-
Paused
Paused. Not accepting reports right now.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
-
Status
Program status changed
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2025-3193 | Versions of the package algoliasearch-helper from 2.0.0-rc1 and before 3.11.2 are vulnerable to Prototype Pollution in the _merge() function in merge.js, which allows constructor.prototype to be written even though doing so throws an error. In the "extreme edge-case" that the resulting error is caught, code injected into the user-supplied search parameter may be exeucted. This is related to but di | High 7.5 | 27 Sep 2025 |
| CVE-2021-23433 | The package algoliasearch-helper before 3.6.2 are vulnerable to Prototype Pollution due to use of the merge function in src/SearchParameters/index.jsSearchParameters._parseNumbers without any protection against prototype properties. Note that this vulnerability is only exploitable if the implementation allows users to define arbitrary search patterns. | Medium 5.9 | 19 Nov 2021 |