Continuous Vulnerability Scanning

Introduced in GitLab 16.4 as an Experiment with two features flags named dependency_scanning_on_advisory_ingestion and package_metadata_advisory_sync. Enabled by default.

This feature is an Experiment and subject to change without notice. If you have any feedback, you can let us know in the feedback issue.
On self-managed GitLab, by default this feature is available. To hide the feature, an administrator can disable the feature flags named dependency_scanning_on_advisory_ingestion and package_metadata_advisory_sync. On, this feature is available.

Continuous Vulnerability Scanning detects new vulnerabilities outside a pipeline. Your projects are automatically scanned whenever advisories are added to the GitLab Advisory Database. Projects that depend on the affected components have new vulnerabilities automatically created.

Continuous Vulnerability Scanning detects vulnerabilities in the latest CycloneDX SBOM reports for the default branch. Dependency Scanning is used to generate these reports.


To enable Continuous Vulnerability Scanning:

On GitLab self-managed only, you can choose package registry metadata to sync in the Admin Area for the GitLab instance.

Requirements for offline environments

For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required to successfully scan CycloneDX reports for vulnerabilities. For more information, see the offline quick start guide.

Supported languages and package managers

The supported files and versions are the ones supported by Dependency Scanning.

Go pseudo versions are not supported. A project dependency that references a Go pseudo version is never considered as affected. This might result in false negatives.

Checking new vulnerabilities

New vulnerabilities detected by Continuous Vulnerability Scanning are visible on the Vulnerability Report. However, they are not listed on the Dependency List or in the pipeline where the affected SBOM component was detected.

After an advisory is added to the GitLab Advisory Database, it might take a few hours before the corresponding vulnerabilities are added to your projects.

Contributing to the vulnerability database

To find a vulnerability, you can search the GitLab Advisory Database. You can also submit new vulnerabilities.