- Top reward
- $15,000
- Top severity paid
- High
- Assets in scope
- 3
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $15,000
- for high bugs, from $500.
- Report as the policy says
- The policy page explains how.
- Replies within 3 days
- As the policy promises.
- Payment
- Proof of identity needed to get paid.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
| Severity | Relative size | Reward |
|---|---|---|
| High |
|
$5,000 |
| Medium |
|
$2,500 |
| Low |
|
$500 |
- Top reward
-
$15,000
Rewards range from $500 to $15,000 based on impact, report quality, and timing of submission
- Lowest reward
-
$500
Rewards range from $500 to $15,000 based on impact, report quality, and timing of submission
- Response
-
Within 3 days
Within 3 business days we will respond with a decision on whether or not the flaw is within scope and what the likely range of bounty will be.
- Hall of fame
-
Yes
Researchers have the option to make their profile information and submission statistics publicly available in our leaderboard .
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, 1 excluded.
Domains 1
- 0din.ai
Products and areas 2
- Affected models can be commercial and/or open source.
- Commonly adopted GenAI models and applications including but not limited to those from OpenAI, Meta, Google, Anthropic, SalesForce, etc.
Out of scope (1)
- Eligible model bugs must exist within the models themselves, as opposed to the software ecosystem around the model.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Mozilla's policy.
While testing
-
You must not exploit the security vulnerability for your own gain.
-
Researchers are encouraged to use test accounts and avoid harming service availability or stability.
-
Submission details must be kept confidential during the validation period (two weeks).
-
You must not have contributed to or be responsible for the vulnerability.
-
You must be the age of majority to be eligible to participate in and receive payment from this Program in your jurisdiction
Not accepted
-
Eligible model bugs must exist within the models themselves, as opposed to the software ecosystem around the model.
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.