HackerOne

As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Retesting enables programs to ask hackers to verify whether a vulnerability has been fixed to secure the protection of their data. If you submit a valid vulnerability report, programs can elect to invite you to retest the vulnerability to verify the fixes.

Upon successful completion of a retest, you’ll receive a bounty as well as +2 reputation.

If you’ve submitted a valid vulnerability for a report, the program can request that you retest the vulnerability to make sure it’s been fixed.

If you’re invited to retest the vulnerability, you’ll receive an email notification to retest the report.

Click View retest in your notification email.

Check to see that the vulnerability has been fixed.

Submit your findings in the Retest findings form at the bottom of the report. The form consists of these fields:

- Are you able to reproduce the vulnerability report?
- Please provide us with a short summary of how you retested the vulnerability and upload any attachments of your validations.

1. Click View retest in your notification email.
2. Check to see that the vulnerability has been fixed.
3. Submit your findings in the Retest findings form at the bottom of the report. The form consists of these fields:
 - Are you able to reproduce the vulnerability report?
 - Please provide us with a short summary of how you retested the vulnerability and upload any attachments of your validations.
4. Click Submit.

The program can either approve or reject your results. If they choose to:

You can track your retesting work under Hacker Dashboard &gt; Retesting. You’ll be able to:

See which retest you need to complete and the time you have left to complete it

- Claim open retests
- See which retest you need to complete and the time you have left to complete it
- View all of your completed retests

Hackers: Learn how retesting works at HackerOne

Retesting

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Action	Scenario	Details
Mark as Resolved	You say the vulnerability is fixed.	You’ll be awarded a bounty. The report will close and will be marked as Resolved.
Retest not performed	You say the vulnerability is fixed.	The program will provide a summary explaining why they’ve rejected the retest. They can choose to request another retest for the vulnerability. The status of the report will be changed to Triaged.
Issue still exists	You say the vulnerability is not fixed.	You’ll be awarded a bounty. The report will revert to Triaged and stay open for the program to implement a fix.
Retest not performed	You say the vulnerability is not fixed.	The program will provide a summary explaining why they’ve rejected the retest. The program can choose to request another retest for the report. The status of the report will be changed to Triaged.

Retesting

How It Works

Managing and Viewing Retests