> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/frontier-defense/vulnerabilities.md).

# Vulnerabilities

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FbzYz0jooNj2ZOy1YMVpg%2Fvulnerabilities.png?alt=media&amp;token=2d4f63af-f8b1-49b8-9cfd-c483db7c2f95" alt=""><figcaption></figcaption></figure>

Track open vulnerabilities through the remediation pipeline. Filter by severity or fix state. View full details without leaving CVEF.

**Vulnerabilities** displays findings across code, OSS dependencies, and containers. It groups findings into OSS Vulnerabilities (CVEs) and Novel Vulnerabilities (LVEs). Each group includes severity and exploitability counts.

Use the filter chips above the table to narrow the list. Available filters are **All**, **Critical**, **High**, **Novel (LVEs)**, **In Fix**, and **Eliminated**.

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Column</strong></td><td><strong>Description</strong></td></tr><tr><td>CVE / ID / LVE</td><td>Vulnerability identifier, such as CVE-2021-23440 or LVE-6232-667720499</td></tr><tr><td>Component</td><td>Package name and version, such as npm:owasp-nodejs-goat:1.3.0</td></tr><tr><td>Source</td><td>Package ecosystem tag: npm, maven, pypi, go, Container, or OSS Dep</td></tr><tr><td>Severity</td><td>Critical, High, or Medium severity badge</td></tr><tr><td>Exploitable</td><td>Yes or no chip indicating whether the vulnerability is exploited in the wild</td></tr><tr><td>Verification Status</td><td>How the finding was confirmed, such as static_analysis, execution_verified, or identified_unverified</td></tr></tbody></table>

### Viewing Vulnerability Details

{% stepper %}
{% step %}

#### Open a vulnerability

Select any vulnerability row. A side panel opens.
{% endstep %}

{% step %}

#### Review OSS vulnerability details

For an OSS vulnerability, review the CVE detail card. It includes the description, severity scores, affected versions, and exploitability.
{% endstep %}

{% step %}

#### Review novel vulnerability details

For a novel vulnerability, use the **Overview**, **Find Details**, and **Fix Details** tabs.

**Overview** includes:

* LVE number, title, and severity
* Exploitability, reachability, and verification status
* CWE bug class, file location, and line number
* Source model, discovery date, repository URL, and branch
  {% endstep %}

{% step %}

#### Return to the list

Close the window to return to the filtered list.
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/frontier-defense/vulnerabilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.