Group Dependency List: Inconsistent API responses for vulnerabilities

Summary

On the Group Dependency List, there are inconsistencies between the vulnerabilities that are shown within the list, and the details view:

Screen Recording 2025-11-24 at 8.36.04 am.mov

In this example, the dependency is shown to have 1 Vulnerability, but when clicking on the badge to reveal the details, nothing is rendered.

There are two endpoints being used:

  1. {namespace}/-/dependencies.json - used to render the list
  2. api/v4/occurrences/vulnerabilities?id={occurenceId} - used to render the detailed vulnerability information

They both return different results. In the case above, 2 returns an empty response.

Steps to reproduce

  1. Navigate to a group's dependency list: https://gitlab.com/groups/gitlab-org/-/dependencies
  2. Click on a line item's vulnerabilities (in the example above "laravel/laravel v7.12.0" demonstrates the bug behaviour)

Example Project

  1. https://gitlab.com/groups/gitlab-org/-/dependencies

What is the current bug behavior?

There are inconsistencies between the list's count and the data that is shown within the detailed view.

What is the expected correct behavior?

The data should match.

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.