> ## Documentation Index > Fetch the complete documentation index at: https://docs.cantina.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Bug Bounty Finding Statuses > Understanding finding statuses for bug bounty programs—from submission to resolution Findings in bug bounty programs are assigned a status that reflects their current state in the review process. Below are the statuses used for Cantina bug bounty programs. | Finding Status | Explanation | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **New** | Once a finding is submitted by the security researcher, it is labelled as New by default. | | **In Review** | The finding has been triaged and is being evaluated by the triage team or in collaboration with the client to determine validity and next steps. | | **Rejected** | Upon review, if the finding does not meet the criteria or is deemed invalid, the triager or client will mark it as Rejected. | | **Duplicate** | A finding is marked as Duplicate when it is the same issue reported by someone else. Duplicates are not rewarded in bug bounty programs. | | **Confirmed** | When the finding is valid, it is labelled as Confirmed. | | **Spam** | The finding is irrelevant, low-quality, automated, or inappropriate. Both triagers and the client can mark this status. | | **Withdrawn** | The researcher has chosen to withdraw the finding. | | **Disputed** | The researcher has set this status to challenge the initial decision and request mediation. | **Duplicate or Rejected and you disagree?** You can set the finding’s status to **Disputed** in Cantina Code to trigger mediation. Only findings in Disputed status are eligible for Cantina’s mediation process. See the [Mediation Process for Bounties](/for-security-researchers/participation-guides/bug-bounty-participation#mediation-process-for-bounties) for how escalation works.