From 18a0d6a5b13489e124f2c074a866a9d453d3a712 Mon Sep 17 00:00:00 2001 From: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com> Date: Thu, 2 Oct 2025 23:16:56 +0700 Subject: [PATCH 1/2] Create SECURITY.md Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com> --- SECURITY.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000000..034e848032 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,21 @@ +# Security Policy + +## Supported Versions + +Use this section to tell people about which versions of your project are +currently being supported with security updates. + +| Version | Supported | +| ------- | ------------------ | +| 5.1.x | :white_check_mark: | +| 5.0.x | :x: | +| 4.0.x | :white_check_mark: | +| < 4.0 | :x: | + +## Reporting a Vulnerability + +Use this section to tell people how to report a vulnerability. + +Tell them where to go, how often they can expect to get an update on a +reported vulnerability, what to expect if the vulnerability is accepted or +declined, etc. From 7c16072fd8d1c33c4fd1cbbec3e7c4c1bc11e720 Mon Sep 17 00:00:00 2001 From: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com> Date: Thu, 2 Oct 2025 23:35:29 +0700 Subject: [PATCH 2/2] Update SECURITY.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com> --- SECURITY.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 034e848032..36a9e38519 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -14,8 +14,10 @@ currently being supported with security updates. ## Reporting a Vulnerability -Use this section to tell people how to report a vulnerability. +We take all security bugs in Mempool seriously. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions. -Tell them where to go, how often they can expect to get an update on a -reported vulnerability, what to expect if the vulnerability is accepted or -declined, etc. +To report a security vulnerability, please use the [GitHub Security Advisory "Report a Vulnerability"](https://github.com/mempool/mempool/security/advisories/new) feature. + +Alternatively, you can email us at security@mempool.space. + +You should receive a response within 48 hours. If the issue is confirmed, we will release a patch as soon as possible depending on complexity.