> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/send/security/report-a-vulnerability.md).

# Report a vulnerability

How to tell Devolutions about a security issue in Devolutions Send.

How to tell Devolutions about a security issue in Devolutions Send.

## Where to report

| CASE                                                                                           | WHERE                                                                                                                                                                                               |
| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Devolutions Send and Devolutions Crypto are in the scope of the Devolutions bug bounty program | Report through the Devolutions YesWeHack program. These reports aren’t accepted by email. The program is by invitation: email your YesWeHack username to `security@devolutions.net` to request one. |
| An issue outside the program’s scope                                                           | Email `security@devolutions.net`                                                                                                                                                                    |

## What to include

* A clear description of the vulnerability, how it can be exploited, and its security impact.
* Complete steps to reproduce, including code snippets, payloads or commands when needed.
* Proof of exploitation, such as screenshots.
* Remediation advice, if possible.

{% hint style="warning" %}
Never include an active Devolutions Send link, a passphrase or a real secret in your report.
{% endhint %}

## What happens next

Devolutions reproduces the issue, gives it a severity score according to CVSS 3.1, and keeps you informed until the case is resolved. Allow a reasonable time frame for feedback. Keep the report confidential until the fix is released in production.

To stay informed, subscribe to [Devolutions security advisories](https://devolutions.net/security/advisories/). Full details: [Devolutions security page](https://devolutions.net/security/).


---

# 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.devolutions.net/send/security/report-a-vulnerability.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.
