- Top reward
- $15,000
- Top severity paid
- Critical
- Assets in scope
- 12
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $15,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Replies within 2 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$15,000 from $10,000 |
| High |
|
$5,000 from $2,500 |
| Medium |
|
$1,000 from $500 |
| Low |
|
$150 |
- Response
-
Within 2 days
Time to first response (from report submit) - 48 hours
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
12 assets you may test, 1 excluded.
Web 7
- cdn.plaid.com Critical
- dashboard.plaid.com Critical
- demo.plaid.com Medium
- my.plaid.com Critical
- plaid.com Medium
- production.plaid.com Critical
- secure.plaid.com Critical
Source code 5
- https://github.com/plaid/plaid-link-android Critical
- https://github.com/plaid/plaid-link-ios Critical
- https://github.com/plaid/plaid-ruby Critical
- https://github.com/plaid/react-native-plaid-link-sdk Critical
- https://github.com/plaid/react-plaid-link Critical
Out of scope (1)
- https://my.plaid.com/data-subject-request-form
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Plaid (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Do not engage in activity that will result in privacy violations, destruction of data, and interruption or degradation of our service.
-
Only interact with accounts you own or with explicit permission of the account holder.
-
Automated scanning (through commercial or open-source scanners like Burp Active Scan or Zap Active Scan) against Plaid properties is not permitted.
-
Please use your [email protected] email when testing.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Unauthenticated/logout/login CSRF
-
Attacks requiring MITM
-
Previously known vulnerable libraries without a working Proof of Concept
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability
-
Missing best practices in SSL/TLS configuration
-
Any activity that could lead to the disruption of our service (DoS)
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
User account enumeration
-
Version disclosure, detailed error messages, and any other findings whose only security impact is ‘attacker reconnaissance’
-
SPF and email antispam 'hygiene' issues
-
Application 'hygiene' issues like cookie subdomain settings or security flags or missing security headers
-
Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue.
-
Reports from automated scanners that have not been validated
-
Homoglyph phishing attacks / domain registration
-
Dependency scan issues
-
Best practices concerns
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 4 minutes 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.
-
Scope added
https://my.plaid.com/data-subject-request-form (out of scope)
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.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Plaid looks forward to working with the security community to find security vulnerabilities in order to keep our business and customers safe.
Program Scope
Any domain/property of Plaid not listed in the Scope, including data repos such as GitHub, PasteBin, etc. may be accepted at Plaid's discretion but is not guaranteed.
SLA
Plaid will make a best effort to meet the following SLAs for hackers participating in our program:
- Time to first response (from report submit) - 48 hours
- Time to triage (from report submit) - 5 business days
- Time to bounty (from triage) - 10 business days
We’ll try to keep you informed about our progress throughout the process.
Non-Disclosure and Confidentiality Policy
- We require that you refrain from disclosing any vulnerabilities to the public or third party. Any disclosure will result in a disqualification from the bug bounty program.
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple qualifying vulnerabilities caused by one underlying issue will be awarded one bounty.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Do not engage in activity that will result in privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- Automated scanning (through commercial or open-source scanners like Burp Active Scan or Zap Active Scan) against Plaid properties is not permitted.
- Violation of any of the program rules, including guidelines around bounty submission formats, are grounds for removal from the bug bounty program.
- Please use your [email protected] email when testing.
Rewards
Plaid provides rewards to vulnerability reporters at its discretion. Reward amounts may vary depending upon the severity of the vulnerability reported and quality of the report.
| Severity | Bounty* | Example Issues |
|---|---|---|
| Critical | $10,000 - $15,000 | Remote Code Execution on servers, SQL Injection |
| High | $2,500 - $5,000 | Significant Authentication or Authorization Bypass / Logic Flaw, Cross-site Scripting, SSRF |
| Medium | $500 - $1,000 | Unrestricted File System Access, Directory Traversal |
| Low | $150 | Information Leakage, Incorrect API access controls, Sub-domain takeover |
* These amounts are indicative and we may reward lower amounts for vulnerabilities that require significant user interaction or that have no significant impact, as we determine at our discretion. We also might pay higher amounts for creative or severe vulnerabilities as we determine at our discretion. Additionally, you only get paid for the first 2 bugs you find if you discover a pattern of vulnerability.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Managing Dashboard Users / Dashboard Team Management
- Clickjacking on pages with no sensitive actions
- Unauthenticated/logout/login CSRF
- Attacks requiring MITM
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Missing best practices in SSL/TLS configuration
- Any activity that could lead to the disruption of our service (DoS)
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- User account enumeration
- Vulnerabilities that require attackers to obtain another user's authenticated session, tokens, or physical access to their devices
- Reports that a webhook URL was accepted or that Plaid sent a request to a customer-configured webhook, including internal or cloud-metadata addresses, unless you show that Plaid retrieved data from internal infrastructure
- Issues that depend on unpatched or outdated browsers or mobile platforms
- Version disclosure, detailed error messages, and any other findings whose only security impact is ‘attacker reconnaissance’
- SPF and email antispam 'hygiene' issues
- Application 'hygiene' issues like cookie subdomain settings or security flags or missing security headers
- Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue.
- Reports from automated scanners that have not been validated
- Rate limit bypasses on sign-in and forgot/reset password endpoints will be considered at discretion of the Plaid security team
- Homoglyph phishing attacks / domain registration
- Dependency scan issues
- Best practices concerns
Getting Setup
You can view our API’s postman docs here:
To start with a full Plaid demo environment, you can view our Pattern project on Github:
Once your Dashboard account is setup, you will have access to Plaid’s sandbox environment. You can then create sample users and data.
Staying Up to Date
To see what’s new at Plaid, you can check out the Changelog section of the Plaid blog.
Thank you for helping keep Plaid and our users safe!