AI bug bounty triage and duplicate checks
Before you submit, a model can check a finding against the program's scope, exclusions, disclosed reports and severity scale. It catches the reports that would close as Duplicate, N/A or Out of scope.
The checks, and what closes otherwise
| Check | Paste | If you skip it |
|---|---|---|
| In scope? | Your scope checklist | Out of Scope: "A submission which is rejected because it is not in scope with the criteria outlined in the bounty brief." (Bugcrowd) |
| Already known? | Disclosed report titles, known issues | Duplicate: "This issue has already been reported or is otherwise previously known by the customer team." (HackerOne) |
| Impact shown? | Your PoC notes | N/A: "The report doesn't contain a valid reproducible issue, and the security implications have not been demonstrated." (HackerOne) |
| Severity | The finding and the scale | HackerOne uses CVSS 3.0, 3.1 or 4.0; Bugcrowd uses the VRT. |
A model sees only what you paste, so it cannot find private duplicates.
The prompt
Check this finding before I submit it to a bug bounty program.1. Is the asset in the scope list? Quote the matching line.2. Does it fall under an excluded vulnerability type?3. Does it match any disclosed report or known issue below?4. Do my notes show impact, or only assume it?5. Suggest a CVSS 4.0 vector and explain each metric.Answer each point separately. Say "unclear" rather than guess. <scope>[your checked scope list]</scope><exclusions>[the program's exclusions]</exclusions><known>[titles of disclosed reports and known issues]</known><finding>[your notes]</finding>Why it pays
Bugcrowd now counts N/A outcomes against your accuracy score, and below 50% you can send 6 reports a week (Bugcrowd, October 2026).
HackerOne requires severity on submission from September 21, 2026, unless a program opts out (HackerOne).
For the score itself, use FIRST's CVSS 4.0 calculator and check each metric the model suggested.
Checks like these run many times a day, so price matters: DeepSeek V4.1 Flash 1017 costs $0.24 in and $0.90 out per 1M tokens.