Support Bulletin: Contrast Scan Local Runner Version Support

  • Updated

Date: September 28, 2026 

To ensure uninterrupted scanning operations, a mandatory annual update is required for Contrast Scan. This update is necessary for the continued use of the local scanner.

What's changing?

The current Contrast Scan local scanner is set to reach its end of life on October 18, 2026. We have released an updated version of the scanner which is available for download.

Critical Action Required: If you are using the scanner locally and do not upgrade to the newly licensed version by October 18, 2026, all pipelines utilizing the scan step will fail.

What does this mean for you?

All customers using the local scanner must update their runner versions before the mid-October expiration date to avoid pipeline disruptions.

Please update your pipelines and scripts to fetch and execute the following updated versions:

  • sast-local-scan-runner: Update to version 2.0.5
  • Contrast-Security-OSS/contrast-local-scan-action: Ensure your pipeline uses the @v1 tag which will soon be updated to use the latest local scanner.
    If you are unable to reference the v1 tag and must use a specific version or hash, please update your tag to v1.0.11.

How to update your scanners

To update your SAST Scanner, you will need to modify the configuration files or scripts used in your CI/CD pipelines (e.g., Jenkins, GitLab, Azure DevOps) or your local scanning environment.

  1. Locate the scanner configuration: Find the pipeline step, shell script, or automation tool where the scanner binary is currently being downloaded or executed.
  2. Update your configurations: For the SAST Scanner: Replace any hardcoded version numbers in your download URLs, API calls, or execution commands with version 2.0.5.                         For the GitHub Action: Ensure your pipeline is configured to use the @1 tag (e.g., uses: Contrast-Security-OSS/contrast-local-scan-action@1). This will automatically pull the latest release without needing a specific version number update.
  3. Verify the update: Trigger a test build or manual scan to ensure the newly licensed version runs successfully and the scan completes without expiration warnings.

For additional information about our support policy, check our Support Reference Guide. If you have any questions, concerns, or would like to discuss this issue further, please don't hesitate to reach out to us at support@contrastsecurity.com.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request