> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/software-composition-analysis-sca-vulnerability-issues/understand-the-vulnerabilities-table.md). # Understand the Vulnerabilities table ## Widgets Use the widgets to identify and prioritize the most urgent issues before opening the detailed table. Selecting a widget value filters the table to matching issues. ### Urgency breakdown The Urgency widget charts the count of open issues per Urgency level. Read the proportions rather than the absolute counts. ### SLA Status Review issues by SLA compliance status. ### Insights Each insight card pairs an **Urgency** level with another risk dimension. Dimensions include SLA status, business criticality, internet exposure, fix availability, dependency type, and traceability completeness. Each card shows the number of issues matching both conditions. ## Vulnerabilities table The table provides a consolidated view of SCA CVE vulnerability issues. Each row represents an issue created when a scanner finding matches a unified policy. It links the vulnerability to its CVE, package, file, repository, and triggering policy. The columns in this table are documented in a shared reference. For descriptions of every available column, the attributes common to all code scan issue tables and the attributes specific to this issue type, see [Issue table attributes reference](/application-security/code-security/code-security-scanners/issue-table-attributes-reference.md). To show or hide any column, select the column picker in the table header. ## Filter and sort the table Use the filter bar at the top of the Vulnerabilities table to narrow results by any filterable column. Common filtering strategies include: * **By severity:** Filter to **Critical** and **High** severity to focus on the most impactful CVE vulnerabilities * **By package:** Filter to a specific package name (such as log4j-core) to scope remediation to a single dependency * **By branch:** Filter to the main or production branch to focus on vulnerabilities that affect production-bound code * **By resolution status:** Filter to **New** to identify untriaged CVE vulnerability issues, or to In Progress to monitor active remediation * **By KEV status:** Filter to **True** to identify vulnerabilities listed in the CISA Known Exploited Vulnerabilities catalog that require immediate attention * **By reachability:** Filter to **Reachable** to focus on vulnerabilities where the vulnerable function is confirmed to be invoked in the application code * **By EPSS score:** Sort by EPSS score (descending) to prioritize vulnerabilities with the highest probability of active exploitation ## Manage issues Right-click on a row in the inventory table to access the following actions * **Change Status**. Modify the status of the issue. Values: New, In Progress, Resolved * **Change Severity**: Modify the severity level of the issue. Values: Critical, High, Medium, Low * **Change Assignee**: Change the user or identity assigned to address the issue * **Copy text to clipboard**: Duplicate selected text for easy pasting elsewhere * **Copy entire row**: Duplicate the entire row of data for easy pasting elsewhere * **Copy issue URL**: Duplicate the URL associated with the issue, to share or reference the issue * **Show/hide rows with the \[severity level]**: Show/hide rows matching the \[severity level] of the selected row --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/software-composition-analysis-sca-vulnerability-issues/understand-the-vulnerabilities-table.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.