Picnic
By Picnic Technologies Vulnerability disclosure program on Self-hosted picnic.app
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 3
- 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]
- 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.
- Hall of fame
-
Yes
Researchers who responsibly disclose valid vulnerabilities will be added to our Security Hall of Fame .
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test.
Domains 2
- picnic.app
- picnic.nl
Products and areas 1
- Picnic systems and applications
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Picnic's policy. "We" in these lines means the program, not this site.
While testing
-
Test only on systems you own or have explicit permission to access
-
Report your finding privately and promptly — do not share it with others before we have resolved it
-
Provide clear, reproducible steps so our team can understand and validate the finding
-
Give us reasonable time to investigate and remediate before any public disclosure
-
Install malware, backdoors, or any malicious software on any system
-
Launch denial-of-service (DoS/DDoS) attacks
-
Use social engineering, phishing, or physical access techniques
-
Access, download, or modify data belonging to other users
-
Use brute force or aggressive automated scanning tools
-
Share or retain sensitive data beyond what is strictly needed to demonstrate the vulnerability
Not accepted
-
Self-XSS — requires the victim to execute the payload in their own browser
-
Missing security headers (CSP, X-Frame-Options, HSTS, etc.) without a working exploit demonstrating real impact
-
Automated scanner output submitted without manual validation or demonstrated impact
-
Theoretical vulnerabilities with no working proof-of-concept
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 5 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.