Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Semtech

By Semtech Corporation Vulnerability disclosure program on HackerOne semtech.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
43
Public CVEs
0
Last change

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.

Pays cash
No This is a non-monetary VDP; no financial rewards are offered.
Response
Within 2 days | First Response | 2 days |
Safe harbor
Full Semtech will not initiate or recommend any law enforcement or civil lawsuits related to such activities

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

43 assets you may test.

Web 27

  • autodiscover.semtech.com Critical No bounty
  • br.learn.semtech.com Critical No bounty
  • chat.semtech.com Critical No bounty
  • collaborate.semtech.com Critical No bounty
  • csm.semtech.com Critical No bounty
  • customercommunity.sierrawireless.com Critical No bounty
  • forum.sierrawireless.com Critical No bounty
  • gitlab.semtech.com Critical No bounty
  • go.semtech.com Critical No bounty
  • help.semtech.com Critical No bounty
  • http://www.airvantage.net Critical No bounty
  • investors.semtech.com Critical No bounty
  • jira.semtech.com Critical No bounty
  • m2mconnectivity.com.au Critical No bounty
  • m2mone.com.au Critical No bounty
  • m2mone.co.nz Critical No bounty
  • partners.sierrawireless.com Critical No bounty
  • partnertraining.semtech.com Critical No bounty
  • qa.airvantage.io Critical No bounty
  • saml.semtech.com Critical No bounty
  • semtech.my.site.com Critical No bounty
  • shop.semtech.com Critical No bounty
  • source.sierrawireless.com Critical No bounty
  • status.sierrawireless.com Critical No bounty
  • stg.semtech.com Critical No bounty
  • www.semtech.com Critical No bounty
  • www.sierrawireless.com Critical No bounty

Wildcard domains 8

  • *.airvantage.net Critical No bounty
  • *airvantage.net Critical No bounty
  • blog*semtech.com Critical No bounty
  • info*semtech.com Critical No bounty
  • *learn.semtech.com Critical No bounty
  • *.sierrawireless.com Critical No bounty
  • *sierrawireless-com.go-vip.net Critical No bounty
  • *vpn*.semtech.com Critical No bounty

Hardware and IoT 5

  • Airlink ALEOS Critical No bounty
  • Airlink XR/RX (>=AOS 6.1) Critical No bounty
  • Any Semtech Hardware Product Critical No bounty
  • LoRa LR Critical No bounty
  • Sierra Wireless Modules Critical No bounty

Desktop and binaries 1

  • Any LoRa Software product Critical No bounty

Products and areas 2

  • Any Semtech Mobile Application Critical No bounty
  • Any Semtech Software Product Critical No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Semtech (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.

Not accepted

  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction

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.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope removed

    *.loracloud.com

  2. Scope added

    Any LoRa Software product

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search 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.

Semtech Corporation and its subsidiaries ("Semtech") looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe. Thank you for your participation in Semtech's Vulnerability Disclosure Program (the "Program"). Below you will find the Semtech Vulnerability Disclosure Policy (the "Policy"). This is a non-monetary VDP; no financial rewards are offered.

Response Targets

Semtech will make a best effort to meet the following SLAs for researchers 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 will keep you informed about our progress throughout the process.

Disclosure Policy

  • • Upon confirmation of a valid report, Semtech will work with you to agree on a reasonable embargo period prior to public disclosure. The duration will reflect the severity and complexity of the vulnerability. During this period, please keep all details of the vulnerability, including any assigned CVE ID, confidential. Semtech will notify you when the Security Bulletin has been published.
  • Follow HackerOne's disclosure guidelines.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

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
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Credentials discovered solely through third-party breach aggregation or monitoring sites (e.g., HaveIBeenPwned, breach databases) where the exposure occurred outside Semtech's current infrastructure. Credentials discovered through active testing of Semtech's current systems, applications, or services remain in scope.

Safe Harbor

You must comply with this Policy and all applicable laws in your jurisdiction in connection with your security research activities or other participation in this Program. Semtech does not authorize, permit, or otherwise allow (expressly or impliedly) any person, including any individual, group of individuals, consortium, partnership, or any other business or legal entity to engage in any security research or vulnerability or threat disclosure activity that is inconsistent with this Policy or the law. If you engage in any activities that are inconsistent with this Policy or the law, you may be subject to criminal and/or civil liabilities. To the extent that any security research or vulnerability disclosure activity involves the networks, systems, information, applications, products, or services of a non-Semtech entity, that third party may independently determine whether to pursue legal action or remedies related to such activities. If you conduct your security research and vulnerability disclosure activities in accordance with the restrictions and guidelines set forth in this Policy: (1) Semtech will not initiate or recommend any law enforcement or civil lawsuits related to such activities, and (2) in the event of any law enforcement or civil action brought by anyone other than Semtech, Semtech will take steps to make known that your activities were conducted pursuant to and in compliance with this Policy.

Thank you for helping keep Semtech and our customers safe!