Vulnerability status

Vulnerability status reflects the resolution and mute status of a vulnerability or affected entity.

Potential states for vulnerabilities

Open: The vulnerability is active.
Resolved: The vulnerability was closed automatically because the root cause is no longer present. For details, see Vulnerability evaluation: Resolution.
Muted (Open): The vulnerability is active but all its affected entities were muted by request.

Filter vulnerabilities by Status to see Open and Resolved vulnerabilities

Resolved vulnerabilities are displayed only once (at the resolution time). Extend the timeframe to include more results. For details, see Timeframe filter.
Filter vulnerabilities by Mute: Status to see Muted (Open) vulnerabilities
Format table by Status

Affected: The entity is affected by the vulnerability.
Resolved: The entity was closed automatically because the root cause is no longer present.
Muted (Affected): The entity is affected by the vulnerability but was silenced by request.
Muted (Resolved): The silenced vulnerability was closed automatically because the root cause is no longer present.

A muted entity that was closed automatically doesn't change its status to Resolved, but to Muted (Resolved).

In the vulnerability details, select View all process groups/View all Kubernetes nodes to navigate to the process group/Kubernetes node overview page related to the vulnerability.
You have the following options:
- Filter by Status to see the affected entities that are Affected or Resolved
- Filter by Mute > Mute: Status to see affected entities that are Muted (Affected) or Muted (Resolved)
- Format affected entities table by Status
- Change the mute status of affected entities