# Findings severity levels

The audit contest is directed at identifying possible vulnerabilities in the project's code. The result of the audit is a report with a list of detected vulnerabilities ranked by severity level:

 

| Severity                                 | Description                                                                                                                        |
| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="color:red;">Critical</mark> | Vulnerabilities leading to the theft of assets, blocking access to funds, or any other loss of funds.                              |
| <mark style="color:yellow;">High</mark>  | Vulnerabilities that cause the contract to fail and that can only be fixed by modifying or completely replacing the contract code. |
| <mark style="color:blue;">Medium</mark>  | Vulnerabilities breaking the intended contract logic but without loss of funds and need for contract replacement.                  |
| <mark style="color:green;">Low</mark>    | Minor bugs that can be taken into account in order to improve the overall quality of the code                                      |

&#x20;

After the stage of bug fixing by the Customer, the findings can be assigned the following statuses:

&#x20;

| Status                                          | Description                                                                                                                                   |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="color:green;">Fixed</mark>         | Recommended fixes have been made to the project code and no longer affect its security.                                                       |
| <mark style="color:yellow;">Acknowledged</mark> | The Customer took into account the finding. However, the recommendations were not implemented since they did not affect the project's safety. |

&#x20;

<br>


---

# Agent Instructions: 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:

```
GET https://docs.strongholdsec.io/audit/findings-severity-levels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.