Canada Goose Inc.
Vulnerability disclosure program on HackerOne canadagoose.com
- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 3
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 2 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 2 days
| First Response | 2 days |
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test.
Web 3
- api.canadagoose.com Critical No bounty
- canadagoose.com Critical No bounty
- service.canadagoose.com Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Canada Goose Inc. (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Do not conduct social engineering, (e.g, spearphishing, vishing, smishing) of Canada Goose personnel, third parties, contractors, or customers
-
Avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
Only interact with accounts you own or with the explicit permission of the account holder.
-
Common Automated Tooling including Acunetix, Nessus, and Qualys should be avoided.
-
Do not compromise the privacy or safety of Canada Goose personnel or any third parties.
-
Do not include any information that may identify an individual other than yourself (such as name, contact information, IP address, or other similar information) in your vulnerability report or any attachments
-
Do not use tiny-urls in reports.
Not accepted
-
Clickjacking on pages with no sensitive actions.
-
Unauthenticated/logout/login CSRF.
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Bugs requiring exceedingly unlikely user interaction (e.g., requiring a user to manually type in an XSS payload)
-
Banner Exposure / Version Disclosure
-
Missing best practices in Content Security Policy
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour 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.
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.
Canada Goose Inc. looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.
Response Targets
Canada Goose Inc. will make reasonable efforts to meet the following response targets for hackers participating in our program:
| Type of Response | SLA in business days |
|---|---|
| First Response | 2 days |
| Time to Triage | 10 days |
| Time to Resolution | depends on severity and complexity |
We’ll use reasonable efforts to keep you informed about our progress throughout the process.
Disclosure Policy
• Follow HackerOne's disclosure guidelines: https://www.hackerone.com/disclosure-guidelines.
Program Rules
• Do not conduct social engineering, (e.g, spearphishing, vishing, smishing) of Canada Goose personnel, third parties, contractors, or customers • Avoid privacy violations, destruction of data, and interruption or degradation of our service. • Only interact with accounts you own or with the explicit permission of the account holder. • Common Automated Tooling including Acunetix, Nessus, and Qualys should be avoided. Such tools include payloads that could trigger state changes or damage production systems or data • Do not compromise the privacy or safety of Canada Goose personnel or any third parties. • Do not compromise the intellectual property or other commercial or financial interests of any Canada Goose personnel or entities, or any third parties. • Do not include any information that may identify an individual other than yourself (such as name, contact information, IP address, or other similar information) in your vulnerability report or any attachments
#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
• Clickjacking on pages with no sensitive actions. • Unauthenticated/logout/login CSRF. • Attacks requiring MITM or physical access to a user's device. • Previously known vulnerable libraries without a working Proof of Concept. • Comma Separated Values (CSV) injection without demonstrating a vulnerability. • Missing best practices in SSL/TLS configuration. • Any activity that could lead to the disruption of our service (DoS). • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS • Bugs requiring exceedingly unlikely user interaction (e.g., requiring a user to manually type in an XSS payload) • Any activity involving Canada Goose Inc. physical locations, including but not limited to conducting physical attacks against assets (e.g., any equipment within Canada Goose facilities, stores, locks, Point of Sale (POS) systems, kiosks) • Banner Exposure / Version Disclosure • Missing best practices in Content Security Policy
#Crafting a Report To help streamline our intake process, we ask that submissions include:
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact. • Description of the reported vulnerability. • Provide your IP address in the bug report. We will keep this data private and only use it to review logs related to your testing activity. • Steps to reproduce the reported vulnerability. • Proof of exploitability (e.g., screenshot, video). • Perceived impact to another user or the organization. • List of URLs and affected parameters. • Other vulnerable URLs, additional payloads, Proof-of-Concept code. • Browser, OS or app version used during testing. • Do not use tiny-urls in reports.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
We may collect information that could reasonably be used to identify you (e.g., IP address). Canada Goose Inc uses this information to evaluate a reported vulnerability and protect products, services or information technology infrastructure. Canada Goose reserves the right to modify or terminate this program at any time.
Thank you for helping keep Canada Goose Inc. and our customers safe!