> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/helm/manage-vulnerabilities/export-vulnerabilities.md).

# Export vulnerabilities

In the **Vulnerabilities** page, you can export all vulnerabilities for a particular product, as well as all notes your team has made in identifying the risk each vulnerability poses to your organization.

There are two ways to export vulnerabilities, either from the **Reports** page or directly from the **Vulnerabilities** table.

**Export vulnerabilities from Reports**

1. Click the **Reports** item in the sidebar to display the **Reports** page.
2. Click the **Export vulnerabilities** button on the **Vulnerabilities CSV** card.

**Export vulnerabilities from the Vulnerabilities page**

1. In **Vulnerabilities**, select the product name and either all versions or a particular version.
2. Click **Export vulnerabilities**. This will export any vulnerabilities that you have not otherwise filtered out.


---

# 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.medcrypt.com/medcrypt-documentation/helm/manage-vulnerabilities/export-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.