misskey/SECURITY.md

21 lines
972 B
Markdown
Raw Normal View History

2021-05-23 20:50:45 +00:00
# Reporting Security Issues
2023-12-25 07:50:41 +00:00
If you discover a security issue in Misskey, please report it by **[this form](https://github.com/misskey-dev/misskey/security/advisories/new)**.
2021-05-23 20:50:45 +00:00
This will allow us to assess the risk, and make a fix available before we add a
bug report to the GitHub repository.
Thanks for helping make Misskey safe for everyone.
2024-11-17 08:35:27 +00:00
2025-02-01 04:57:39 +00:00
> [!note]
> CNA [requires](https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_5-2_Description) that CVEs include a description in English for inclusion in the CVE Catalog.
>
> When creating a security advisory, all content must be written in English (it is acceptable to include a non-English description along with the English one).
2024-11-17 08:35:27 +00:00
## When create a patch
If you can also create a patch to fix the vulnerability, please create a PR on the private fork.
> [!note]
> There is a GitHub bug that prevents merging if a PR not following the develop branch of upstream, so please keep follow the develop branch.