What's new
Product version
1.5.2
Release date
May 19, 2026
Brief description
This release focuses on improving the system's stability and quality.
Summary
- Fixed the following issues:
- The wrong Git provider type was sent to SASTAV when scanning Bitbucket repositories;
- Scans failed to start when authenticating with a Personal Access Token or username and Password;
- The status was handled incorrectly when saving LDAP settings;
- URL format validation failed when testing an SSH connection to Bitbucket Cloud;
- The severity level of vulnerabilities was determined incorrectly when importing CodeScoring scan results in SARIF format;
- The severity level of vulnerabilities was determined incorrectly when importing AppScreener SAST scan results in SARIF format;
- An access error occurred when removing a project's binding to the SASTAV tool;
- Access rights were checked incorrectly when working with the SASTAV tool's additional settings;
- Changes weren't saved when the scan source type was changed to a Git repository;
- Editing the connection parameters for the global SASTAV integration (URL, username, and Password) caused the system to freeze.
Bug fixes (Big Fixes)
| Issue (bug) | Fix description |
|---|---|
| The wrong Git provider type was sent to SASTAV when scanning Bitbucket repositories | What changed for the user: When scanning Bitbucket repositories in SASTAV, the provider type is set to “Bitbucket” |
| Scans failed to start when authenticating with a Personal Access Token or username and Password | What changed for the user: Scans now start and run successfully when authenticating with a username and Password or a Personal Access Token |
| The status was handled incorrectly when saving LDAP settings | What changed for the user: The system now correctly reports that the parameters were applied successfully |
| URL format validation failed when testing an SSH connection to Bitbucket Cloud | What changed for the user: Connection testing now works correctly with repositories that use SSH addresses |
| The severity level of vulnerabilities was determined incorrectly when importing CodeScoring scan results in SARIF format | What changed for the user: The system now correctly uses the CVSS score to set the vulnerability severity level |
| The severity level of vulnerabilities was determined incorrectly when importing AppScreener SAST scan results in SARIF format | What changed for the user: The system now correctly uses the CVSS score to set the vulnerability severity level |
| An access error occurred when removing a project's binding to the SASTAV tool | What changed for the user: Project bindings to the SASTAV tool can now be removed and saved successfully |
| Access rights were checked incorrectly when working with the SASTAV tool's additional settings | What changed for the user: Users can perform these operations if they have access to at least one project |
| Changes weren't saved when the scan source type was changed to a Git repository | What changed for the user: You can now change the scan source type to a Git repository successfully |
| Editing the connection parameters for the global SASTAV integration (URL, username, and Password) caused the system to freeze | What changed for the user: The new URL, username, and Password for the global SASTAV integration are now saved and updated in the system |
REST API changes
Feedback and support
Conclusion
We're improving the user experience and responding to issues as they arise.
Thank you to our users for reporting issues that helped us prepare this update.