In GitLab's vulnerability report, what do Needs triage, Confirmed, Dismissed and Resolved mean, and why does a fixed vulnerability stay open?
answer
- four statuses, one default
- dismissal always needs a reason
- fixed is not the same as resolved
- no longer detected goes in the activity log
basics
~20 sNeeds triage is a new vulnerability's starting status; Confirmed means verified; Dismissed means judged not worth fixing, with a reason; Resolved means fixed. A fix only logs No longer detected; a person or a vulnerability management policy must set Resolved.
solid answer
~50 sThe vulnerability report, an Ultimate feature, lists vulnerabilities found on the default branch. Each starts as **Needs triage**. Someone moves it to **Confirmed** after checking it is real, or to **Dismissed** with one of five reasons (**Acceptable risk**, **False positive**, **Mitigating control**, **Used in tests**, **Not applicable**) and a required comment; dismissed vulnerabilities are ignored if later scans detect them again. When a later scan no longer finds it, GitLab adds **No longer detected** to the record's activity but leaves the status alone, because it cannot tell a deliberate fix from a side effect of other changes. Someone must verify it and set **Resolved**, or a vulnerability management policy can auto-resolve matches. A resolved vulnerability that is reintroduced goes back to **Needs triage**. Changing status needs the Security Manager, Maintainer or Owner role; the Developer role lost that permission in GitLab 17.0. Records cannot be deleted.
go deeper
Recall the four statuses and that every new vulnerability starts at Needs triage.
Explain why No longer detected does not change status, the five dismissal reasons, and which roles may change status since 17.0.
Run triage as a routine: review no-longer-detected records, enforce honest dismissal reasons, and automate low-risk clean-up with a vulnerability management policy.
Decide what may be dismissed by whom and what policy may resolve automatically, balancing auditability against a report nobody can keep up with.
## Where vulnerabilities come from In GitLab, a scanner's result on a feature branch is a **finding**. When the branch is merged and a scan on the **default branch** detects it, it becomes a **vulnerability** with a permanent record. The **vulnerability report**, available on GitLab Ultimate for projects and groups, lists those records and is where a security team triages them. Records cannot be deleted. Dismissing one leaves an audit trail of who, when and why, so a permanent history always remains. ## The four statuses | Status | Meaning | How it gets there | |---|---|---| | **Needs triage** | Nobody has assessed it yet | Default for every newly detected vulnerability | | **Confirmed** | Someone checked it and it is real | Set by a person | | **Dismissed** | Assessed and accepted, or not a real issue | Set by a person or a policy, with a reason | | **Resolved** | Fixed or no longer present | Set by a person or by a vulnerability management policy | The usual lifecycle runs Needs triage, then Confirmed, then Resolved, or Needs triage straight to Dismissed. One transition runs backwards: if a resolved vulnerability is reintroduced and detected again, its record comes back with the status **Needs triage**. ## Dismissing with a reason A dismissal must carry one of five reasons and a comment, entered in the comment box that GitLab 17.9 added to status changes: - **Acceptable risk**: known, not fixed or mitigated, but an acceptable business risk. - **False positive**: the scanner reported something that is not there. - **Mitigating control**: another safeguard gives equivalent protection. - **Used in tests**: the finding is test code or test data. - **Not applicable**: known and not fixed, but in a part of the application that will not be updated. Dismissed vulnerabilities are ignored when later scans detect them again, so a dismissal is a long-lived decision, not a snooze. The report can filter dismissed records by reason, which keeps them reviewable. Triage can also start earlier: a finding dismissed from a feature branch pipeline's **Security** tab keeps that status when the branch is merged into the default branch, so the vulnerability does not arrive as Needs triage. ## Why a fixed vulnerability stays open When a scan on the default branch no longer detects a vulnerability, GitLab does **not** change its status. It adds **No longer detected** to the record's activity log, links the commit that removed it where it can, and leaves the status at Needs triage or Confirmed. A vulnerability can stop being detected because of a deliberate fix or as a side effect of other changes, and GitLab cannot tell which, so someone has to check, then set **Resolved**. The report's activity filter **No longer detected** lists exactly these records, which makes a weekly clean-up practical. ## Automating the clean-up A **vulnerability management policy**, an Ultimate policy type, can apply status changes consistently: - **Auto-resolve** vulnerabilities that are no longer detected and match criteria such as scanner and severity. The **GitLab Security Policy Bot** then sets them to Resolved. - **Auto-dismiss** matches, for example findings in test files with the reason **Used in tests**. - **Override severity** for vulnerabilities that match specific identifiers. The policy only touches vulnerabilities whose status is **Needs triage** or **Confirmed**. It runs when a pipeline runs against a tracked branch, or when advisory scanning detects new vulnerabilities. ## Who can change status Changing a vulnerability's status needs the **Security Manager**, **Maintainer** or **Owner** role for the project, or a custom role with the `admin_vulnerability` permission. The **Developer** role had that permission until it was removed in **GitLab 17.0**. A developer can still see the report and fix the code, but cannot dismiss what they find inconvenient. ## A workable triage routine 1. Filter the report to **Needs triage**, sorted by severity, and confirm or dismiss the critical and high records first. 2. Insist on an honest dismissal reason and comment; **Acceptable risk** and **False positive** mean different things to an auditor. 3. Review **No longer detected** records and resolve the ones whose fix you can verify. 4. Hand the routine cases, such as low-severity records that vanish, to a vulnerability management policy. 5. Watch for records returning to Needs triage: a reintroduced vulnerability usually means a regression.
- In GitLab, which vulnerabilities can a vulnerability management policy change, and who appears as the actor?Only vulnerabilities with the status Needs triage or Confirmed; dismissed and resolved records are left alone. When the policy auto-resolves records that are no longer detected, the GitLab Security Policy Bot user sets them to Resolved, so the activity log shows the policy rather than a person made the change.
- In GitLab, why should a team prefer Confirmed over leaving a real vulnerability at Needs triage?Needs triage means nobody has looked yet, so a backlog of it hides which records are understood and which are unknown. Confirming records that are real separates assessed risk from unassessed noise, and merge request approval policies can target such records through the confirmed vulnerability state.
- GitLab marks a vulnerability Resolved as soon as a scan stops detecting it.
- A Developer can dismiss vulnerabilities in GitLab 19.4.
- Dismissing a GitLab vulnerability deletes its record from the report.
- A dismissal in GitLab needs no reason; it simply hides the record.
- A reintroduced vulnerability stays Resolved because it was fixed once.
Assumes GitLab 19.4; the Developer role lost the permission to change vulnerability status in 17.0, and the status-change comment box arrived in 17.9.