Skip to content

Update private vulnerability reporting guidance #6

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

Merged
devclinic merged 1 commit into from
Aug 11, 2026
Merged

Update private vulnerability reporting guidance #6

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
2 changes: 1 addition & 1 deletion SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Only the latest tagged beta is supported for security fixes.

Please do **not** open a public issue for a suspected vulnerability involving HID access, installer/update behaviour, local data, or a protocol write path.

After publishing this repository, use GitHub’s **Security → Report a vulnerability** private reporting flow. The repository owner must enable private vulnerability reporting in the GitHub repository settings before the first public release. If that setting is not yet enabled, contact the repository owner privately rather than posting technical exploit details publicly.
Use GitHub's **Security > Report a vulnerability** private reporting flow for this repository. This sends the report privately to the maintainers so details can be assessed and addressed before public disclosure.

Useful reports include a minimal reproduction, affected version, expected and observed behaviour, and only the smallest redacted diagnostic excerpt needed to understand the issue.

Expand Down
Loading