> 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/review-and-fix/severity-levels-in-findings.md).

# Severity levels in findings

The severity levels of Snyk API and Web findings

Snyk API & Web assigns a severity level to each finding to summarize its overall risk based on the following factors:

* The likelihood of the vulnerability being found and exploited.
* The skills required to exploit the vulnerability.
* The impact of exploiting the vulnerability.

For example, a vulnerability that is easy to find, easy to exploit, and has a high impact is likely classified with a high severity.

Different findings for the same vulnerability can have different severity levels depending on the context in which Snyk API & Web finds the vulnerabilities. Multiple factors can influence this context, which Snyk API & Web considers to lower or raise the severity level. For example, the severity of a finding can be higher or lower depending on whether the scanned target has authentication configured.

## Severity levels

The following table describes the different severity levels.

| Severity     | Description                                                                                                                                                                   | Examples                                               |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| DAoGv5pJ2QPn | These findings require immediate attention and remediation due to their potentially devastating impact.                                                                       | SQL Injection, OS Command Injection                    |
| CEQJw2Dg2qUX | These findings can have a direct impact on the application security, either clients or service owners, for example, by granting the attacker access to sensitive information. | Reflected Cross-Site Scripting, Path Traversal         |
| CLg1PflLeJ0i | Medium findings do not usually have an immediate impact alone, but combined with other findings, can lead to a successful compromise of the application.                      | Cross-Site Request Forgery, Unencrypted Communications |
| dzwfjdzNIMju | Findings where either the exploit is not trivial, or the finding cannot be exploited by itself.                                                                               | Directory Listing, Clickjacking                        |

## Related information

Visit [Interpret target scan results](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/interpret-target-scan-results.md) for more information about findings.


---

# 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://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/severity-levels-in-findings.md?ask=<question>&goal=<endgoal>
```

`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.