> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/vulnerabilities-detected/vulnerability-updates.md).

# Vulnerability updates

How Snyk API & Web updates its detected vulnerabilities

Snyk API & Web continuously adds and updates vulnerability detection to maintain strong protection and high security standards.

## How Snyk stays current

The Snyk team continuously follows and investigates recent industry vulnerabilities, monitors security advisories, and collaborates with industry experts to stay current with cybersecurity threats. The engine team uses diverse sources and detection techniques to keep the vulnerability knowledge base up to date. This approach lets Snyk maintain an extensive, current database of vulnerabilities.

## Where to find vulnerability information

Stay informed about the latest developments through these resources:

* Visit [Vulnerability types detected](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/vulnerabilities-detected/vulnerability-types-detected.md) for a list of the vulnerability types Snyk detects.
* Visit [Snyk Vulnerabilities Knowledge Base](https://probely.com/vulnerabilities/) for a detailed list of all vulnerabilities Snyk detects.


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/vulnerabilities-detected/vulnerability-updates.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.