Raspberry Pi Foundation
Vulnerability disclosure program on security.txt raspberrypi.org
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 6
- 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 by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 5 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
Please note this is not a bug bounty program, and we do not offer rewards for disclosures.
- Response
-
Within 5 days
Respond to plausible reports within 5 business days, and work with you to understand and validate your report;
- Safe harbor
-
Partial
In participating in our vulnerability disclosure program in good faith, we ask that you:
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 3 excluded.
APIs 1
- APIs
Domains 1
- raspberrypi.org
Source code 1
- open source repositories under the Raspberry Pi Foundation GitHub organisation
Wildcard domains 1
- *. raspberrypi.org
Products and areas 2
- hosted services
- web apps
Out of scope (3)
- raspberrypi.com
- Assets or other equipment not owned by parties participating in this policy.
- Raspberry Pi hardware
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Raspberry Pi Foundation's policy. "We" in these lines means the program, not this site.
While testing
-
Report any vulnerability you’ve discovered promptly;
-
Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
-
Do not engage in any form of social engineering (e.g. phishing), denial of service attacks, or any action that could degrade services for real users;
-
Avoid high-volume or aggressive scanning tools that may degrade service availability;
-
Use only the Official Channels to discuss vulnerability information with us;
-
Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
-
Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
-
Only interact with test accounts you own or with explicit permission from the account holder; and
-
Do not engage in extortion.
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 2 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.