Skip to content

Add security section to README #1735

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
veluca93 merged 2 commits into from
Oct 26, 2026
+19 −0
Merged

Add security section to README #1735

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
381c1fc
Add security section to README
veluca93 Oct 26, 2026
59ef8cb
Fix typo in README regarding GitHub Security Advisory
veluca93 Oct 26, 2026
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
19 changes: 19 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,3 +77,22 @@ find an updated list at <http://cms-dev.github.io/testimonials.html>.
If you used CMS for a contest, selection, or a similar event, and want
to publicize this information, we would be more than happy to hear
from you and add it to that list.

Security
--------

If you (or your agent) believe that you found a security vulnerability
in CMS, please follow these steps:

1) Ensure that the security issue can actually be reproduced.
2) Check that the vulnerability is compatible with CMS's threat model.
In particular:

- A "vulnerability" caused by a configuration key that explicitly
mentions needing modification is not a vulnerability.
- CMS assumes that the network that services will use for RPCs
is trusted. Anything that can be triggered by sending RPCs only
is not a vulnerability.

3) If you did (1) and (2), please open a GitHub Security Advisory under
the "Security" tab.
Loading