Skip to content

doc: mention GitHub private vulnerability reporting in SECURITY.md #9409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vincenzopalazzo wants to merge 1 commit into from
+12 −4
Closed

doc: mention GitHub private vulnerability reporting in SECURITY.md #9409

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,18 @@ We have a 3 month release cycle, and the last two versions are supported.

## Reporting a Vulnerability

To report security vulnerabilities, please send an email to:
- `security@blockstream.com`

Note: This email address is exclusively for vulnerability reporting.
To report security vulnerabilities, you can either:

- **Use GitHub private vulnerability reporting** (preferred): click
["Report a vulnerability"](https://github.com/ElementsProject/lightning/security/advisories/new)
in the [Security](https://github.com/ElementsProject/lightning/security) tab.
This creates a private draft security advisory that is only visible to
you and the maintainers, and gives us a single place to discuss the
issue, collaborate on a fix, and coordinate disclosure (including
requesting a CVE).
- **Send an email** to `security@blockstream.com` (GPG key below).

Note: The email address is exclusively for vulnerability reporting.

For all other inquiries/communication, please refer to the [Reach Out to Us](https://github.com/ElementsProject/lightning?tab=readme-ov-file#reach-out-to-us) section in our README.

Expand Down
Loading