> 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/check-whether-a-particular-vulnerability-impacts-your-products.md).

# Check whether a particular vulnerability impacts your products

From any page in Helm, you can search on which products are impacted by a particular vulnerability across all products using the global search box in the top navigation bar. This enables you to quickly prioritize new threats.

1. In the global search box on any page, select **Vuln ID** from the search drop-down. Alternately, you can go directly to the **Discover** page to run searches. Either way, your last search results will display on this page, if you need to return to them.
2. Type in a vulnerability ID (e.g., CVE-123-4567), then press Enter to run the search.
3. From **Actions > …**, you can then jump to either viewing **Software Bill of Materials (SBOM)** or **Vulnerabilities**.

#### **Jump to product**

If you jump to this product, you’ll be able to see which product and product versions contain that component and version. From the **Actions > …** button, you can choose to view more details, add a review note, view review history, and more.

#### Jump to vulnerabilities

If you jump to vulnerabilities for this dependency component, you can view the applicable vulnerabilities. From the **Actions > …** button, you can manage each vulnerability.


---

# 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/check-whether-a-particular-vulnerability-impacts-your-products.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.