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 for more information about findings.