Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

incident.io

Vulnerability disclosure program on Self-hosted incident.io

Accepting reports
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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 However, we do not offer monetary rewards for vulnerability disclosures.
Response
Within 5 days After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days.
Safe harbor
Partial This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause incident.io or partner organizations to be in breach of any legal obligations.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

1 asset you may test.

Domains 1

  • incident.io

Rules

What the policy asks of you, and the bug types it won't reward, quoted from incident.io's policy.

While testing

  • Access unnecessary, excessive or significant amounts of data.
  • Modify data in incident.io’s systems or services.
  • Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
  • Disrupt incident.io’s services or systems.
  • Social engineer, ‘phish’ or physically attack the Organization's staff or infrastructure.
  • Demand financial compensation in order to disclose any vulnerabilities.
  • Always comply with data protection rules and must not violate the privacy of any data incident.io holds.
  • Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

Not accepted

  • non-exploitable vulnerabilities
  • reports indicating that the services do not fully align with “best practice”, for example missing security headers
  • email security configuration, for example SPF, DKIM, or DMARC policy settings
  • TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support
  • any form of denial of service

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.