- Top reward
- $200,000
- Top severity paid
- Critical
- Assets in scope
- 24
- Public CVEs
- 21
- Last change
At a glance
What to know before you start testing.
- Pays up to $200,000
- for critical bugs.
- Report by email
- [email protected]
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$200,000 from $50,000 |
| High |
|
$50,000 from $14,000 |
| Medium |
|
$14,000 from $1,000 |
| Low |
|
$1,000 from $500 |
Scope
24 assets you may test, 10 excluded.
Web 10
- accounts.shopify.com Critical
- admin.shopify.com Critical
- arrive-server.shopifycloud.com Critical
- help.shop.app Medium
- partners.shopify.com Critical
- shop.app Critical
- shop.com Critical
- shopifyinbox.com Medium
- shopify.plus Critical
- your-store.myshopify.com Critical
Wildcard domains 7
- *.pci.shopifyinc.com Critical
- *.shopifycloud.com Medium
- *.shopify.com Medium
- *.shopifycs.com Critical
- *.shopify.io Medium
- *.shopifykloud.com Medium
- *.shopifysvc.com Medium
Source code 1
- https://github.com/Shopify/* Medium
Products and areas 6
- Shopify Developed Apps Medium
- Shopify Mobile Applications Critical
- Shopify Third Party Apps Medium No bounty
- Shopify Third Party Store Medium No bounty
- Shop Minis Medium
- Sidekick Critical
Out of scope (10)
- Other
- supplier-portal.shopifycloud.com
- cdn.shopify.com
- community.shopify.com
- community.shopify.dev
- livechat.shopify.com
- shopifyevents.com
- shopifypartnerships.com
- shopify.photo
- *.email.shopify.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Shopify (via HackerOne)'s policy.
While testing
-
Only test against stores you created using your HackerOne `YOURHANDLE @ wearehackerone.com` registered email.
-
Do not attempt to gain access to, or interact with stores you didn’t create.
-
Do not disclose issues publicly before resolution or without permission.
-
Do not contact Shopify Support as part of your testing or to ask about the bounty program, to pre-validate reports nor to ask for updates.
-
You must report any discovered vulnerability to Shopify as soon as you have validated the vulnerability.
Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
-
Scope +
Added to scope: shop.com
-
Scope +
Added to scope: shopify.photo
-
Scope +
Added to scope: help.shop.app
-
Scope +
Added to scope: shopifypartnerships.com
-
Scope +
Added to scope: shopifyevents.com
-
Scope +
Added to scope: Shop Minis
-
Scope +
Added to scope: *.shopifysvc.com
-
Scope +
Added to scope: Sidekick
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
shop.com
-
Scope added
help.shop.app
-
Scope added
Shop Minis
-
Scope added
*.shopifysvc.com
-
Scope added
shopify.photo (out of scope)
-
Scope added
shopifyevents.com (out of scope)
-
Scope added
shopifypartnerships.com (out of scope)
-
Scope removed
Authentication & ATO
-
Scope removed
academy.shopify.com (out of scope)
-
Scope removed
linkpop.com
-
Scope added
Sidekick
-
Scope removed
investors.shopify.com (out of scope)
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-55685 | React Router is a router for React. In versions 7.0.0 through 7.17.0, the manifest endpoint could be accessed via unauthenticated targeted requests that would put heavy load on the server and slow down response times. This issue is a follow up to CVE-2026-42342, and does not does not impact React Router applications using Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<Router | High 8.7 | 27 Jul 2026 |
| CVE-2026-53666 | React Router is a router for React. In versions 6.4.0 through 7.17.0, if application code was written in a way that allows attacker-supplied input to overwrite certain aspects of errors caught by the SSR process, then it was possible for an attacker to trigger unexpected constructor execution on the client, which would in turn trigger an outbound network request. This is only possible with very sp | Medium 6.1 | 27 Jul 2026 |
| CVE-2026-53667 | React Router is a router for React. In versions 7.11.0 through 7.17.0, the RSCErrorHandler is missing protocol validation, allowing for redirects from untrusted sources. This issue is a follow up to CVE-2026-53667, and only affects consuming applications if they are using the unstable RSC APIs. This issue has been fixed in version 7.18.0. | Medium 6.9 | 27 Jul 2026 |
| CVE-2026-53668 | React Router is a router for React. In versions 6.30.2 through 6.30.4 and 7.9.6 through 7.12.0, applications that allow open redirects are vulnerable to XSS. An attacker could craft a malicious link that redirects users to an unexpected external site or that exploits an XSS vector.This issue has been fixed in version 7.13.0. | Medium 6.9 | 27 Jul 2026 |
| CVE-2026-53669 | React Router is a router for React. Versions 6.0.0 through 7.17.0 are vulnerable to Open Redirtect through use of backslashes in <Link> and useNavigate. This issue is a follow up to CVE-2025-68470 and has been fixed in version 7.18.0. | Medium 5.1 | 27 Jul 2026 |
| CVE-2026-42211 | React Router is a router for React. In versions 7.0.0 through 7.14.1, when using Framework Mode, a combination of steps could potentially allow unauthorized remote code execution (RCE) through external requests. This attack requires the application code to have an existing prototype pollution vulnerability, which can then be leveraged in a 2-step attack where the second step triggers unauthorized | High 8.1 | 2 Jun 2026 |
| CVE-2026-42342 | React Router is a router for React. In versions 7.0.0 through 7.14.x of react-router and versions 2.10.0 through 2.17.4 of @remix-run/server-runtime, certain crafted requests can consume disproportionate server resources via unbounded path expansion in the __manifest endpoint, resulting in response time degradation and/or service unavailability for end users. This affects React Router Framework Mo | High 7.5 | 2 Jun 2026 |
| CVE-2026-40181 | React Router is a router for React. In versions 7.0.0 through 7.14.0 and 6.7.0 through 6.30.3, certain URLs passed to the redirect function can trigger an open redirect to an external domain due to path values starting with // being reinterpreted as protocol-relative URLs. The level of impact depends on the validation done by the application prior to returning the redirect. This does not impact ap | Medium 6.6 | 2 Jun 2026 |
| CVE-2026-34077 | React Router is a router for React. In versions 7.7.0 through 7.13.1, when using React Router's unstable React Server Components (RSC) APIs, there is a potential client-side Cross-Site Scripting (XSS) vulnerability in the RSC redirect handling if redirects come from untrusted sources. This does not impact applications that are not using the unstable RSC APIs in React Router. This is patched in ver | High 7.5 | 2 Jun 2026 |
| CVE-2026-33245 | React Router is a router for React. In versions 7.7.0 through 7.13.1, when using React Router's unstable React Server Components (RSC) APIs, there is a potential client-side Cross-Site Scripting (XSS) vulnerability in the RSC redirect handling if redirects come from untrusted sources. This does not impact applications that are not using the unstable RSC APIs in React Router. This is patched in ver | High 8.0 | 2 Jun 2026 |
| CVE-2026-33244 | React Router is a router for React. In versions 7.5.1 through 7.13.1, when using Framework Mode with pre-rendering enabled, improper neutralization of the HTTP `Location` header value can permit Cross-Site Scripting (XSS) in the statically generated HTML files if the redirect location comes from an untrusted source. This does not impact applications using Declarative Mode (`<BrowserRouter>`) or Da | Medium 5.4 | 2 Jun 2026 |
| CVE-2026-39862 | Tophat is a mobile applications testing harness. Prior to 2.5.1, Tophat is affected by remote code execution via crafted tophat:// or http://localhost:29070 URLs. The arguments query parameter flows unsanitized from URL parsing through to /bin/bash -c execution, allowing an attacker to execute arbitrary commands on a developer's macOS workstation. Any developer with Tophat installed is vulnerable. | Medium 6.3 | 8 Apr 2026 |
| CVE-2026-34060 | Ruby LSP is an implementation of the language server protocol for Ruby. Prior to Shopify.ruby-lsp version 0.10.2 and ruby-lsp version 0.26.9, the rubyLsp.branch VS Code workspace setting was interpolated without sanitization into a generated Gemfile, allowing arbitrary Ruby code execution when a user opens a project containing a malicious .vscode/settings.json. This issue has been patched in Shopi | High 7.1 | 31 Mar 2026 |
| CVE-2026-21884 | React Router is a router for React. In @remix-run/react version prior to 2.17.3. and react-router 7.0.0 through 7.11.0, a XSS vulnerability exists in in React Router's <ScrollRestoration> API in Framework Mode when using the getKey/storageKey props during Server-Side Rendering which could allow arbitrary JavaScript execution during SSR if untrusted content is used to generate the keys. There is no | High 8.2 | 10 Jan 2026 |
| CVE-2026-22029 | React Router is a router for React. In @remix-run/router version prior to 1.23.2 and react-router 7.0.0 through 7.11.0, React Router (and Remix v1/v2) SPA open navigation redirects originating from loaders or actions in Framework Mode, Data Mode, or the unstable RSC modes can result in unsafe URLs causing unintended javascript execution on the client. This is only an issue if you are creating redi | High 8.0 | 10 Jan 2026 |
| CVE-2026-22030 | React Router is a router for React. In @remix-run/server-runtime version prior to 2.17.3. and react-router 7.0.0 through 7.11.0, React Router (or Remix v2) is vulnerable to CSRF attacks on document POST requests to UI routes when using server-side route action handlers in Framework Mode, or when using React Server Actions in the new unstable RSC modes. There is no impact if Declarative Mode (<Brow | Medium 6.5 | 10 Jan 2026 |
| CVE-2025-59057 | React Router is a router for React. In @remix-run/react versions 1.15.0 through 2.17.0. and react-router versions 7.0.0 through 7.8.2, a XSS vulnerability exists in in React Router's meta()/<Meta> APIs in Framework Mode when generating script:ld+json tags which could allow arbitrary JavaScript execution during SSR if untrusted content is used to generate the tag. There is no impact if the applicat | High 7.6 | 10 Jan 2026 |
| CVE-2025-61686 | React Router is a router for React. In @react-router/node versions 7.0.0 through 7.9.3, @remix-run/deno prior to version 2.17.2, and @remix-run/node prior to version 2.17.2, if createFileSessionStorage() is being used from @react-router/node (or @remix-run/node/@remix-run/deno in Remix v2) with an unsigned cookie, it is possible for an attacker to cause the session to try to read/write from a loca | Critical 9.1 | 10 Jan 2026 |
| CVE-2025-68470 | React Router is a router for React. In versions 6.0.0 through 6.30.1 and 7.0.0 through 7.9.5, an attacker-supplied path can be crafted so that when a React Router application navigates to it via navigate(), <Link>, or redirect(), the app performs a navigation/redirect to an external URL. This is only an issue if you are passing untrusted content into navigation paths in your application code. This | Medium 6.5 | 10 Jan 2026 |
| CVE-2022-29230 | Hydrogen is a React-based framework for building dynamic, Shopify-powered custom storefronts. There is a potential Cross-Site Scripting (XSS) vulnerability where an arbitrary user is able to execute scripts on pages that are built with Hydrogen. This affects all versions of Hydrogen starting from version 0.10.0 to 0.18.0. This vulnerability is exploitable in applications whose hydrating data is us | Medium 6.3 | 18 May 2022 |
| CVE-2020-8176 | A cross-site scripting vulnerability exists in koa-shopify-auth v3.1.61-v3.1.62 that allows an attacker to inject JS payloads into the `shop` parameter on the `/shopify/auth/enable_cookies` endpoint. | Medium 6.1 | 2 Jul 2020 |
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.
Shopify's Bug Bounty Program
We reward security researchers for finding and reporting vulnerabilities that help keep our platform secure. Our bug bounty program offers rewards up to $200,000 and bonuses for outstanding contributions.
Here’s what you can expect:
- Quick review and triage of reports with high-quality evaluations.
- Full transparency on report decisions.
- Prompt bounty awards after triage, except in rare cases.
We value all contributions, from minor issues to critical vulnerabilities, as they help enhance Shopify’s security.
Early Access Program
A special invite-only program where select researchers get early access to Shopify features before they're widely released. This exclusive opportunity lets you discover vulnerabilities in our newest innovations while earning bounties.
Criteria for invitation:
- Submitted 4 or more reports over the past 2 years.
- 50% or higher rate of success on those reports
Please note, invitations are extended at Shopify's discretion based on quality contributions to our security ecosystem.
Getting started
- Review and understand the participation rules, the list of assets in scope, and the list of ineligible issues.
- Familiarize yourself with the
@wearehackerone.comemail address which must be used when creating a Shopify account. This alias is provided by HackerOne and you can learn more about it in their documentation. - Create a Shopify account using this link and follow the registration process.
- You must test only against stores you have created. Testing against live merchants is prohibited and can result in reports being closed as
Not Applicableand/or your disqualification from the Shopify bug bounty program. - Consult Shopify Help Center for further information on how to build a store and to discover platform features. For newest product updates, keep an eye on our Core Change Log and Partners Blog.
If you need further clarification of the rules or scope of our bug bounty program, please don't hesitate to contact us at [email protected].
Eligibility
The scope of the bug bounty program is limited to the assets listed on the scope page for this program. Valid vulnerabilities on any asset not explicitly listed in scope may be accepted but are ineligible for a reward. As a general rule:
- Reports which do not demonstrate relevant security impact to Shopify or our Merchants by providing a functional proof of concept will be closed as N/A.
- We reward researchers based on the scenario that yields the highest overall severity score , provided that the scenario is plausible and directly linked to the root issue. In cases where multiple reports share the same root cause, these will be closed as Duplicate.
- We will only award and triage reports when the root cause is under our control.
- IDOR eligibility will be evaluated considering the identifier predictability, the data accessed and overall impact on the service.
- Reports of a vulnerability disclosing sensitive PII will be evaluated on a case by case basis, considering the overall impact on Shopify's merchant data.
Typical Bounty Amounts
Bounty amounts will be determined using Shopify's Bug Bounty Calculator. In most cases, we will only triage and reward vulnerabilities with a score greater than 0. A score under 3 will result in a $500 bounty. Scores greater than or equal to 3 will be determined by the calculator. In rare cases, we may choose to accept and award a bonus for an issue with a score of 0 when we see a high potential for future security impact and make a change as a result of the report. Bonuses are determined as a percentage (10% of what the bounty is estimated at for an exploitable issue), with a minimum of $500 and a maximum of $5,000.
While our bounty table states the minimum bounty per severity, scores for non-core properties listed in scope will be determined with Environment Score modifiers set to Low for Confidentiality, Integrity, and Availability Requirements.
Leaked Credentials
In alignment with HackerOne’s guidance and terms, Shopify accepts reports of leaked credentials, including Authentication material for Shopify APIs and/or Shopify infrastructure. Hackers should submit the leaked credentials to the program and should not test their validity beyond authenticating and then immediately deauthenticating - without exercising any functionality. Likewise, Hackers should not share these credentials beyond their report to the program.
Rules for participation
The following rules must be followed in order for any rewards to be paid:
- Eligibility for Rewards
- Only test against stores you created using your HackerOne
YOURHANDLE @ wearehackerone.comregistered email. - Do not attempt to gain access to, or interact with stores you didn’t create.
- Follow all reporting rules.
- Do not disclose issues publicly before resolution or without permission.
- Only test against stores you created using your HackerOne
- Program Modifications
- Shopify reserves the right to modify rules or invalidate submissions at any time.
- Shopify may cancel the bug bounty program without notice at any time.
- Contact Restrictions
- Do not contact Shopify Support as part of your testing or to ask about the bounty program, to pre-validate reports nor to ask for updates. Violating this will disqualify you from receiving a reward and may result in a program ban.
- Employment Status
- You are not an employee of Shopify
- Shopify employees must report bugs to the internal bug bounty program.
- Vulnerability Reporting
- You must report any discovered vulnerability to Shopify as soon as you have validated the vulnerability.
Failure to follow any of the foregoing rules will disqualify you from participating in this program.
- General Rules
- Reports must demonstrate relevant CVSS impact to Shopify, Shop users, our partners or our merchants with a functional proof of concept. Reports without this will be closed as N/A.
- Rewards are based on the highest CVSS score scenario that is plausible and linked to the root issue. Multiple reports with the same root cause will be closed as Duplicate.
- You hereby represent, warrant and covenant that any content you submit to Shopify is an original work of authorship and that you are legally entitled to grant the rights and privileges conveyed by these terms. You further represent, warrant and covenant that the consent of no other person or entity is or will be necessary for Shopify to use the submitted content.
- By submitting content to Shopify, you irrevocably waive all moral rights which you may have in the content.
- All content submitted by you to Shopify under this program is licensed under the MIT License.
- Notes
- This program is not open to individuals who are on sanctions lists, or who are in countries on sanctions lists.
- You are responsible for any tax implications resulting from payouts depending on your country of residency and citizenship.
- Shopify reserves the right to cancel this program at any time and the decision to pay a bounty is entirely at our discretion. Your testing and submission must not violate any law, or disrupt or compromise any data that is not your own.
- There may be additional restrictions on your ability to submit content or receive a bounty depending on your local laws.