🪐
Cantina Docs
  • 🪐Welcome to Cantina
  • 🤝Services
    • Security Reviews
    • Competitions
    • Bug Bounty
    • Guilds
    • Public Goods
  • 💵Referral program
  • 📄Public Reports
  • 👑Reputation
  • 👥Cantina Account
    • 🔷Claim an Account
    • 🔷Company Account
      • 🔹Create a Company Account
      • 🔹Managing users
      • 🔹Company Dashboard
      • 🔹Company Reviews
    • 🔷Security Researcher Account
      • 🔹Create Security Researcher Account
      • 🔹Security Researcher Dashboard
      • 🔹Calendar
      • 🔹Reviews
      • 🔹KYC and Payments
  • 💻Cantina Code
    • 🕵️Cantina Code for Security Researchers
      • 🔶Code Review
        • 🔸Download content and toggle sidebar
        • 🔸Highlighting code
      • 🔶Findings
        • 🔸Findings Submission
        • 🔸Findings Labels
        • 🔸Findings Status
        • 🔸Add code to existing finding
        • 🔸Examples
      • 🔶Chat
      • 🔶Reports
      • 🔶Comments & Pings
      • 🔶Diagrams & Formulas
    • 🏢Cantina Code for Companies
      • 🗄️Responding to Pings
      • 🗄️Responding to Findings
      • 🗄️Report Generation
  • 🏆Cantina Competitions
    • 🕵️For Security Researchers
      • 🔶Payments
      • 🔶Teams
      • 🔶Finding Status
      • 🔶Finding Labels
    • 🏢For Companies
      • 🗄️Competition Submission Template
    • 🧑‍⚖️Judging Process
      • 📜Finding Severity Criteria
      • 📜Scoring
      • 📜Judging Phase
      • 📜Escalation Process
    • 🤝 Fellowship Steward Model
  • 💰 Cantina Bounties
    • 🕵️For Security Researchers
      • 🔶Bug Bounty Finding status
    • Bounty Severity Classification
    • Mediation Process for Bounties
  • ✅ Cantina Bug Bounty Coverage
    • Cantina Coverage Details
  • ❓FAQ
    • ❔FAQ Competitions
    • ❔FAQ Security Reviews
  • 🔗Links
Powered by GitBook
On this page
  1. 💰 Cantina Bounties
  2. For Security Researchers

Bug Bounty Finding status

Below you can find a list with all the finding statuses used for bug bounty programs.

Finding Status
Explanation

New

Once a finding is submitted by the security researcher, it will be labelled as new by default.

In Review

The finding has been triaged and is currently being evaluated, either by the triage team or in collaboration with the client, to determine its 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's the same issue reported by someone else. Duplicates are not rewarded in Bug Bounty programs.

Confirmed

When the finding is valid, it will be labelled as confirmed.

Spam

When a finding is marked as spam, it typically refers to the issue reported being irrelevant, low-quality, automated and inappropriate. Both the triagers and the client can mark this status for findings.

Withdrawn

If the researcher submits an issue and decides to withdraw it for any reason, the finding will be labelled as "Withdrawn".


PreviousFor Security ResearchersNextBounty Severity Classification

Last updated 9 days ago

🕵️
🔶