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

Arlo Cash Rewards

By Arlo Technologies, Inc. Bug bounty on Bugcrowd arlo.com

Accepting reports
Go to program
Top reward
$10,000
Top severity paid
Critical
Assets in scope
33
Public CVEs
3
Last change

At a glance

What to know before you start testing.

Pays up to $10,000
for critical bugs, from $25.
Report on Bugcrowd
Submit through the program page.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Bugcrowd lists as the payout for each severity.

Severity Reward
Critical $4,500 from $500
High $1,500 from $250
Medium $600 from $50
Low $100 from $25
Safe harbor
Partial You may only exploit, investigate, or target security bugs against your own accounts and/or your own devices.

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

Earlier reward tables (1)
  • 11 Nov 2026 to 11 Nov 2026: Critical up to $4,500

Scope

33 assets you may test, 6 excluded.

Hardware and IoT 16

  • Arlo All-In-One Sensor (Home Security System)
  • Arlo Base Station
  • Arlo Cellular & Battery Backup (Home Security System)
  • Arlo Chime 2
  • Arlo Essential 2 & 3 (indoor & outdoor camera, doorbell)
  • Arlo Go v2
  • Arlo Home Security System
  • Arlo Pro 3 Floodlight
  • Arlo Pro 5S
  • Arlo Pro 6
  • Arlo Pro SmartHub
  • Arlo Safe Button
  • Arlo Ultra 2
  • Arlo Wired Floodlight
  • Arlo Wire-Free Outdoor Siren (Home Security System)
  • Arlo Wireless Video Doorbell

APIs 5

  • https://mcs.arlo.com
  • https://myapi.arlo.com
  • https://partnerapi.arlo.com
  • https://*-prod.arlo.com
  • https://updates.arlo.com

Web 5

  • https://beta.arlo.com
  • https://*dev*.arlo.com
  • https://my.arlo.com
  • https://*qa*.arlo.com
  • https://www.arlo.com

Wildcard domains 3

  • *.arlocloud.com
  • *.arlo.com (subdomains impacting production customer-facing services)
  • *.arloxcld.com

Android apps 2

  • Arlo Safe Android App
  • Arlo Secure Android App

iOS apps 2

  • Arlo Safe iOS App
  • Arlo Secure iOS App
Out of scope (6)
  • cvrstreaming*.arlo.com
  • https://*streaming*.arlo.com
  • http://community.arlo.com
  • http://research.arlo.com
  • https://investor.arlo.com
  • http://survey.arlo.com

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Arlo Cash Rewards (via Bugcrowd)'s policy.

While testing

  • You may only exploit, investigate, or target security bugs against your own accounts and/or your own devices.
  • Testing must not violate any law, or disrupt or compromise any data or access data that is not yours; intentional access of customer data other than your own is prohibited.
  • If you inadvertently access proprietary customer, employee, or business related information during your testing, the information must not be used, disclosed, stored, or recorded in any way.
  • Your testing activities must not negatively impact Arlo, Arlo’s products or services generally, or Arlo's online environment availability or performance.
  • You must not be the author of the code with the vulnerability.
  • You must not be an Arlo employee, contractor, or a family member of an employee or contractor.

Not accepted

  • Products that reached End-Of-Life stage
  • Duplicate reports of security issues, including security issues identified internally.
  • Automated scanning attacks.
  • Social engineering (e.g. phishing, vishing).
  • Physical attacks such as office access (e.g., open doors, tailgating).
  • Distributed Denial of Service attacks and Denial of Service attacks.
  • UI bugs, UX bugs, and spelling mistakes.
  • Violations of licenses or other restrictions applicable to any vendor's product.
  • Vulnerabilities that are a result of malware.
  • Issues related to email misconfiguration (DMARC, etc.).
  • Any session management vulnerabilities related to www.arlo.com.
  • Any leaked credentials for community.arlo.com, my.arlo.com and www.arlo.com.
  • Any issues related to investor.arlo.com

Summarised with AI from the program policy on Bugcrowd, 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 added

    https://*qa*.arlo.com

  2. Scope added

    https://*dev*.arlo.com

Public CVEs

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

Search NVD
CVESeverityPublished
CVE-2021-31505 Medium 6.8 29 Jun 2021
CVE-2019-3949 Critical 9.8 9 Jul 2019
CVE-2019-3950 Critical 9.8 9 Jul 2019

Original policy

Copied from bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

About Arlo Cash Rewards Program This program encourages and rewards contributions by developers and security researchers who help make Arlo’s products more secure. Arlo provides monetary rewards and kudos for qualifying vulnerability submissions to this program. For submissions outside the scope of this program, please submit to the Arlo Kudos Rewards Program . NETGEAR products have their own Bug Bounty program. Please click the following link to NETGEAR Cash Rewards Program . Only vulnerabilities found in the latest version of the above are eligible. Targets listed below denote Cloud Infrastructure that support in-scope devices and are included in scope: A note about business impact Arlo appreciates the efforts and contributions from the security research community. In order to provide researchers with timely and accurate rewards, Arlo requests that submitters include a statement about perceived impact to arlo, along with the submission details. Not only will this help Arlo reproduce, rate and reward your findings in a timely manner -- it is likely to help improve the severity score of your finding as well!

Targets

Out of Scope: All Arlo products and properties not explicitly denoted in Targets, excluding High Impact Submissions as described below All vulnerabilities submitted to the NETGEAR Cash Rewards Program Priority and Reward Guidelines The Arlo Product Security team, at their sole discretion, determines the nature and impact of the vulnerabilities disclosed including, but not limited to, leveraging CVSS rating methodology to identify the appropriate payouts. The first valid submission to alert Arlo of a previously unknown issue qualifies for reward. Arlo builds products using a common platform and framework. Multiple products sometimes inherit the same vulnerability. When determining bounty awards, Arlo grants a single award that accounts for all affected products. All issues around login and access are of particular concern. Most login submissions classified as P5s will likely be elevated to P4 or greater issues. High Impact Rewards Arlo rewards submissions that Arlo determines meets a below High Impact outcome. Arlo includes all products and services in scope for these rewards. Cash Rewards will be awarded based on the following: $10,000 Unauthorized Access to all Arlo cloud storage video files. Unauthorized Access to all Arlo live video feeds. $3,000 Remote Unauthorized access to only a single Arlo account’s live video feed (via the publicly accessible internet - i.e. not on the same LAN). Remote Unauthorized access to only a single Arlo account’s cloud storage video files (via the publicly accessible internet - i.e. not on the same LAN). Remote Unauthorized access to full Arlo database of customer information. Program Exclusions Products that reached End-Of-Life stage Duplicate reports of security issues, including security issues identified internally. Certain low to medium severity issues only affecting non-production environments (e.g. dev or staging environments) will be analyzed on a case-by-case basis and may be excluded. Automated scanning attacks. Social engineering (e.g. phishing, vishing). Physical attacks such as office access (e.g., open doors, tailgating). Distributed Denial of Service attacks and Denial of Service attacks. UI bugs, UX bugs, and spelling mistakes. Violations of licenses or other restrictions applicable to any vendor's product. Vulnerabilities that are a result of malware. Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded. Issues determined to be low impact such as reflected XSS without demonstrable impact may be excluded. Self-exploitation, such as self-XSS or self-DoS (unless it can be used to attack a different account) are excluded. Discovery of any in-use service whose version contains known vulnerabilities (such as a specific version of OpenSSL, Apache, Tomcat, etc.) without a demonstration of intrusion, information retrieval, or service disruption using that vulnerability. Issues related to email misconfiguration (DMARC, etc.). Issues related to rate limiting, unless they affect high risk areas (authentication, authorization, etc.). Submissions will be analyzed on a case-by-case basis and may be excluded. Any session management vulnerabilities related to www.arlo.com. Any leaked credentials for community.arlo.com, my.arlo.com and www.arlo.com. Any issues related to investor.arlo.com Legal Terms and Conditions In addition to these Terms and Conditions regarding the Arlo Responsible Disclosure Program (the "Program"), there may be additional restrictions depending upon applicable local laws. The parties to this Agreement are you and Arlo Technologies, Inc. "Arlo" refers to Arlo Technologies, Inc. and its affiliates. By submitting the security bug, you affirm that you have not disclosed and agree that you will not disclose the security bug to anyone other than Arlo. Absent Arlo's prior written consent, any disclosure outside of this process would violate this Agreement. You agree that money damages may not be a sufficient remedy for a breach of this paragraph by you and that Arlo will be entitled to specific performance as a remedy for any such breach. Such remedy will not be deemed to be the exclusive remedy for any such breach but will be in addition to all other remedies available at law or equity to Arlo. By submitting information about a potential security bug, you are granting Arlo a worldwide, royalty-free, non-exclusive license to use your submission for the purpose of addressing security bugs in Arlo’s products and services. In the event of substantially duplicate submissions, Arlo may at its discretion provide a Reward only for the earliest received submission. Eligibility for Rewards, determination of the recipients, and amount of Reward is at the discretion of Arlo. If issues reported to our bug bounty program affect a third party or another vendor, Arlo reserves the right to forward details of the issue along to the party without further discussion with the researcher. You are responsible for all taxes associated with and imposed on any Reward you may receive from Arlo. You may only exploit, investigate, or target security bugs against your own accounts and/or your own devices. Testing must not violate any law, or disrupt or compromise any data or access data that is not yours; intentional access of customer data other than your own is prohibited. If you inadvertently access proprietary customer, employee, or business related information during your testing, the information must not be used, disclosed, stored, or recorded in any way. Inadvertent access of the data must be declared within your submission. Your testing activities must not negatively impact Arlo, Arlo’s products or services generally, or Arlo's online environment availability or performance. Arlo may choose not to remediate at its sole discretion. This Agreement constitutes the entire agreement of the parties with respect to the items listed above. This Agreement is covered by California law. This Agreement may be amended or modified only by a subsequent agreement in writing. If any portion of this Agreement is found to be illegal or unenforceable, then the parties will be relieved of their responsibilities arising under such a portion, but only to the extent that such portion is illegal or unenforceable. You must not be the author of the code with the vulnerability. You must not be an Arlo employee, contractor, or a family member of an employee or contractor. ARLO RESERVES THE RIGHT TO MODIFY OR CANCEL THE ARLO RESPONSIBLE DISCLOSURE PROGRAM AT ANY TIME WITHOUT NOTICE. ALL PARTICIPANTS AND SUBMISSIONS ARE STRICTLY VOLUNTARY. THIS OFFER IS VOID WHERE PROHIBITED BY LAW AND IN PARTICIPATING, YOU MUST NOT VIOLATE ANY LAW. YOU ALSO MUST NOT DISRUPT ANY SERVICE OR COMPROMISE ANYONE’S DATA. Rules This bounty follows Bugcrowd’s Public Disclosure Policy . Requests to disclose the results of a submission will be considered on a case by case basis and require explicit prior written consent from Arlo.

Arlo Devices (in scope)

If you have a device, you get access to more features to test. The majority of the Arlo platform and available attack surface is only made available to people who have access to an Arlo Device (listed in the table below).Researchers are encouraged to purchase or otherwise get their hands on Arlo Devices as this is the best opportunity to find high-value, interesting bugs. Purchasing an Arlo Device will not only give Researchers Access to find bugs on the device itself, but will also provide access to the Arlo User Interface. Worth noting, Arlo has introduced new devices at competitive price points (in some cases under $40) which will help allow you to test more thoroughly.

All Other Production Arlo Targets (in scope)

2025-10-06 Update: The following sites are excluded from the target scope effective immediately: community.arlo.com, survey.arlo.com, research.arlo.com 2025-09-02 Update: The bounty for P3 priority submissions is now set in the range of $150–400. Please note that only high impact subdomain takeover submissions, as determined by the Security Team, are eligible for payout. Depending on severity and demonstrated impact, such submissions may qualify for the higher end of the P3 reward range ($400) or, in exceptional cases, may be reclassified as P2–P1 priority issues. Submissions related to the arlostreaming and cvrstreaming subdomains will no longer be accepted. 2024-01-31 Update: the bounty for P3 priority submissions now falls under the range $150-400. In particular, low impact subdomain takeover submissions will be awarded $150. We will still consider certain high impact subdomain takeover submissions for the higher end of P3 rewards ($400) or even P2-P1 priorities, on a case by case basis. 2024-09-03 Update: any reports on specific IPs (no Arlo domain/subdomain) must include a supporting video showing the browser accessing the IP, opening the TLS certificate details to confirm the certificate belongs to Arlo, and detailed steps showing successful exploitation. It is OK to include other supporting evidence such as a Shodan screenshot showing the IP / Arlo hostname(s) / Arlo certificate, but please note this is not enough on its own since the system's certificate snapshot taken by Shodan will be from hours/days/months earlier and by the time your report is submitted the instance could have been owned by other entities (in fact, this happens often, hence this update).

Non-production Environments (Dev/QA/CAT/Test/Staging) (in scope)

Non-production environments