- Top reward
- $150
- Top severity paid
- Not published
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $150
- top reward, from $25.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Paid by PayPal, store credit
- No identity requirement stated.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Top reward
-
$150
$100 to $150 via PayPal and/or store credit = CVSS Score 6.5 - 10.0
- Lowest reward
-
$25
$25 to $50 via PayPal and/or store credit = CVSS Score 0.0 - 6.5
- Safe harbor
-
Partial
We appreciate these types of research activities, but will not tolerate any actions that put our users at risk:
- Hall of fame
-
Yes
To researchers who have reported valid security vulnerabilities can opt to be added to our hall of fame listed here in the "Hall of Fame": https://www.adafruit.com/responsibledisclosurethanks/
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 3 excluded.
Domains 2
- adafruit.com
- adafruitdaily.com
Wildcard domains 2
- *adafruit.com
- *adafruitdaily.com
Out of scope (3)
- adafruit-circuit-python.s3.amazonaws.com
- makecode.adafruit.com
- makecode.adafruit.com (Microsoft).
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Adafruit's policy. "We" in these lines means the program, not this site.
While testing
-
Do not attempt to access, modify, destroy, or disclose our users' information.
-
Do not attempt to deface or degrade our services.
-
Do not violate applicable law.
-
Submissions must include written instructions for reproducing the vulnerability.
-
If reporting vulnerabilities as a video, we ask you to not post POCs publicly without our consent to video-sharing sites such as Youtube, Vimeo .
-
In the case that you need to share a video please ensure it is password protected.
-
We ask you do not publicly disclose your submission until Adafruit has evaluated the impact.
Not accepted
-
Missing best practices in SSL/TLS configuration
-
Missing email best practices (invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.)
-
Software version disclosure, server banners, descriptive error messages, or informational header issues
-
CORS issues without a working PoC demonstrating exploitability
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Self-XSS, self-exploitation, and attacks requiring unlikely user interaction
-
Vulnerabilities only affecting users of outdated or unpatched browsers
-
XMLRPC: pingback and getUsersBlogs methods are disabled; reports for other methods will be reviewed
-
Brute force, credential stuffing, or password spraying attacks. Reports attempting to compromise real user accounts will not be accepted.
-
Attacks requiring MITM or physical access to a user's device
-
Social engineering (e.g., phishing, vishing, smishing)
-
Any activity that could lead to the disruption of our service (DoS)
-
Generic scanner or AI-generated reports without a validated, reproducible exploit
-
Reports of spam
-
Broken links and typos, including misspelled domains in historical blog content
-
Information-stealer logs or exposed credentials (dark web, pastebin, Telegram, etc.) unless tied to an active, ongoing breach
-
New user email validation: registered users are not required to validate their email address; this is by design
-
Account squatting preventing users from registering with certain email addresses
-
Public wishlists: wishlists are private by default; users explicitly opt in to make them public
-
adafruit-circuit-python.s3.amazonaws.com: this S3 bucket is intentionally public for CircuitPython board firmware distribution
-
Adafruit IO (AIO) keys on GitHub belonging to third-party users: these belong to independent projects, not Adafruit infrastructure
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 6 hours 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.