Skip to content

Move vulnerability reporting to GitHub private vulnerability reporting - #971

Open
chrnorm wants to merge 4 commits into
mainfrom
github-vuln-reporting
Open

Move vulnerability reporting to GitHub private vulnerability reporting#971
chrnorm wants to merge 4 commits into
mainfrom
github-vuln-reporting

Conversation

@chrnorm

@chrnorm chrnorm commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Proposed at the 2026-08-27 maintainers meeting: switch vulnerability reporting from the PGP-encrypted email process to GitHub private vulnerability reporting, which is already enabled on this repository.

  • Rewrites SECURITY.md, which still pointed at Common Fate's email, docs link, and old PGP key
  • Adds a coordinated vulnerability disclosure policy aligned with the EU Cyber Resilience Act: a clear reporting contact point, 5-business-day acknowledgement, remediation without undue delay, free security fixes via standard release channels, and public advisories with CVEs once fixed
  • Keeps granted-support@fwdcloudsec.org as a fallback channel for reporters without GitHub accounts
  • Fixes the stale docs.commonfate.io security link in the README

Companion PRs update the docs site and website.

Replace the PGP-encrypted email process with GitHub private
vulnerability reporting, and add a coordinated vulnerability
disclosure policy aligned with the EU Cyber Resilience Act.
Email remains as a fallback reporting channel. Also update the
stale docs.commonfate.io security link in the README.
@chrnorm
chrnorm force-pushed the github-vuln-reporting branch from 904615b to 44d503e Compare August 27, 2026 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants