- Top reward
- $10,000
- Top severity paid
- Critical
- Assets in scope
- 5
- Public CVEs
- 10
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $10,000
- for critical bugs, from $50.
- Report by email
- [email protected]
- No public write-ups
- Keep findings private.
Rewards
What Bugcrowd lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$5,000 from $1,000 |
| High |
|
$1,600 from $500 |
| Medium |
|
$800 from $250 |
| Low |
|
$400 from $50 |
Earlier reward tables (1)
- 11 Nov 2026 to 11 Nov 2026: Critical up to $5,000
Scope
5 assets you may test.
Hardware and IoT 2
- https://www.wyze.com/products/wyze-cam
- Wyze Cam V3
Web 2
- https://auth.wyze.com
- https://my.wyze.com
APIs 1
- https://api.wyzecam.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Wyze Bug Bounty (via Bugcrowd)'s policy.
While testing
-
Testing is only authorized on the targets listed as in scope.
-
do not target other user's data (use one of your other sets of credentials)
-
delete/remove/edit parts of the site
-
engage any sort of DoS attack
-
compromise any target's ability to function for other users
-
please sign up for an account using your @bugcrowdninja.com email address
Not accepted
-
DoS Attacks
-
Brute Force Attacks
-
Anything not mentioned in scope will be considered out of scope
Summarised with AI from the program policy on Bugcrowd, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 2 minutes 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.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2024-6246 | Wyze Cam v3 Realtek Wi-Fi Driver Heap-Based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Wyze Cam v3 IP cameras. Authentication is not required to exploit this vulnerability. The specific flaw exists within the Realtek Wi-Fi kernel module. The issue results from the lack of proper va | High 8.8 | 22 Nov 2024 |
| CVE-2024-6247 | Wyze Cam v3 Wi-Fi SSID OS Command Injection Remote Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Wyze Cam v3 IP cameras. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of SSIDs embedded in scanned QR codes. The issue results from the lack of prop | Medium 6.8 | 22 Nov 2024 |
| CVE-2024-6248 | Wyze Cam v3 Cloud Infrastructure Improper Authentication Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Wyze Cam v3 IP cameras. Authentication is not required to exploit this vulnerability. The specific flaw exists within the run_action_batch endpoint of the cloud infrastructure. The issue results fro | High 7.5 | 22 Nov 2024 |
| CVE-2024-6249 | Wyze Cam v3 TCP Traffic Handling Stack-Based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Wyze Cam v3 IP cameras. Authentication is not required to exploit this vulnerability. The specific flaw exists within the TUTK P2P library. The issue results from the lack of proper validation o | High 8.8 | 22 Nov 2024 |
| CVE-2024-37066 | A command injection vulnerability exists in Wyze V4 Pro firmware versions before 4.50.4.9222, which allows attackers to execute arbitrary commands over Bluetooth as root during the camera setup process. | Medium 6.8 | 19 Jul 2024 |
| CVE-2023-6322 | A stack-based buffer overflow vulnerability exists in the message parsing functionality of the Roku Indoor Camera SE version 3.0.2.4679 and Wyze Cam v3 version 4.36.11.5859. A specially crafted message can lead to stack-based buffer overflow. An attacker can make authenticated requests to trigger this vulnerability. | High 7.2 | 15 May 2024 |
| CVE-2023-6323 | ThroughTek Kalay SDK does not verify the authenticity of received messages, allowing an attacker to impersonate an authoritative server. | Medium 4.3 | 15 May 2024 |
| CVE-2023-6324 | ThroughTek Kalay SDK uses a predictable PSK value in the DTLS session when encountering an unexpected PSK identity | High 8.1 | 15 May 2024 |
| CVE-2019-12266 | Stack-based Buffer Overflow vulnerability in Wyze Cam Pan v2, Cam v2, Cam v3 allows an attacker to run arbitrary code on the affected device. This issue affects: Wyze Cam Pan v2 versions prior to 4.49.1.47. Wyze Cam v2 versions prior to 4.9.8.1002. Wyze Cam v3 versions prior to 4.36.8.32. | High 7.6 | 30 Mar 2022 |
| CVE-2019-9564 | A vulnerability in the authentication logic of Wyze Cam Pan v2, Cam v2, Cam v3 allows an attacker to bypass login and control the devices. This issue affects: Wyze Cam Pan v2 versions prior to 4.49.1.47. Wyze Cam v2 versions prior to 4.9.8.1002. Wyze Cam v3 versions prior to 4.36.8.32. | High 7.5 | 30 Mar 2022 |
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
No technology is perfect and Wyze believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. We are excited for you to participate as a security researcher to help us identify vulnerabilities in our web app and API. Good luck, and happy hunting! Ratings/Rewards: For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.
Targets
Testing is only authorized on the targets listed as in scope. Any domain/property of Wyze not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to Wyze, you can report it to [email protected]. However, be aware that it is ineligible for rewards or points-based compensation. Target Information: Wyze products/devices may share the same source code and features if a vulnerability is found in one of them and the same issue is reported in another device that shares this code it will count as only one valid finding and will be flagged as a duplicate. Access: Targets are accessible via public internet, please note that before reaching https://auth.wyze.com/ you need to sign up for Wyze account, please click here You are testing on production. Behavior that compromises the stability and integrity of the site is out of scope. For example, do not target other user's data (use one of your other sets of credentials), delete/remove/edit parts of the site, engage any sort of DoS attack, and/or compromise any target's ability to function for other users. If you believe that you have found a vulnerability of this nature, please stop further testing and report it. Credentials: To gain access to the application, please sign up for an account using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here . To sign up for Wyze account, please click here Focus Areas: Wyze Cam V3 Wyze Cam V4 Out-of-Scope DoS Attacks Brute Force Attacks Anything not mentioned in scope will be considered out of scope If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via Bugcrowd Supoort before going any further.