Webhook not triggered when vulnerability is auto-resolved by GitLab Bot

Summary

When a vulnerability is auto-resolved by the GitLab Bot using a vulnerability management policy (e.g., “auto-resolve vulnerabilities that are no longer detected”), no webhook is triggered, even though the vulnerability’s status changes to Resolved. This breaks automation workflows relying on webhook notifications.

Steps to reproduce

1. Configure a group or project webhook with vulnerability events enabled (tested with direct webhook endpoint)
2. Introduce a detectable vulnerability
3. Set up a vulnerability management policy to auto-resolve vulnerabilities that are no longer detected
4. Remove the secret and push again to trigger auto-resolution by GitLab Bot
5. Observe:
   • ✅ Webhook is triggered when status is manually changed to Resolved
   • ❌ No webhook is triggered when GitLab Bot changes the status to Resolved

Example Project

What is the current bug behavior?

Webhook is only triggered for manual status changes.

What is the expected correct behavior?

Webhook should be triggered when a vulnerability is resolved, regardless of whether it was manual or automatic.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.