Release Date: May 4, 2026

Hey everyone,

This release brings a long-requested workflow improvement for hunters: the ability to save report submissions as drafts so you can work at your own pace without losing progress. Alongside that, we've shipped a wide range of functional fixes, UI improvements, and security patches that keep the platform running smoothly for everyone. Read on for the full details!

✨ New Features

📝 Save Report as Draft

Previously, hunters had to complete their entire report submission in one sitting — navigating away or closing the tab meant starting over. This was especially frustrating for complex findings that require time to document thoroughly. We've now added a SAVE AS DRAFT button to the report submission form, allowing hunters to save their progress at any point — even if required fields haven't been filled out yet. A success or failure toast notification will confirm whether the draft was saved. Saved drafts remain fully editable until they are formally submitted.

📂 Submitted and Drafts Sub-Tabs on the Report Submission Page

With drafts now a core part of the submission workflow, hunters needed a clear way to tell their in-progress work apart from already-submitted reports. We've introduced two sub-tabs under the Report Submission section in the side panel: Submitted and Drafts. The Submitted tab shows all formally submitted reports, while the Drafts tab displays reports that have been saved but not yet submitted. Both tabs support sorting by most recent and oldest submission, and the Submitted tab includes filters by Program Type, Severity, and Status.

🔍 Filter by Weakness on Report Submissions

Hunters with a large number of submissions previously had no way to narrow down their list by vulnerability type, making it difficult to find specific reports quickly. We've added a filter by weakness to the report submissions list, allowing hunters to search for a specific weakness and see only the reports that match it.

🛠️ Functional Bugfixes

• We fixed an issue that prevented Jira projects from loading when organization users attempted to send a report to Jira from the Reports page.
• We fixed a data type mismatch in the External Pentest Scoping Questionnaire where the API asset field was being submitted as an array from the frontend while the backend expected a string, causing an error that blocked form submission.
• We fixed an issue that caused an error when editing a custom web app asset in the External Pentest Scoping Questionnaire.
• We fixed an issue where the SAVE button in the Bounty Rewards settings page was not saving changes successfully when organization users attempted to update their bounty reward configuration.
• We fixed a white screen error that appeared when accessing the Billing page for both BBP and VDP programs.
• We fixed the Post an Update button in the Program Updates page, which was unresponsive and did not open the post update flow when clicked.
• We fixed an error that was triggered when an organization owner or admin attempted to change the role of an organization member from the Members page.
• We fixed an issue on the Forgot Password page where typing an email address did not activate the submit button, preventing users from initiating a password reset on both production and staging environments.