Skip to content

Additional guidelines for security reports #9659

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

Open
wiredfool wants to merge 2 commits into
base: main
Choose a base branch
from
+14 −0
Open

Additional guidelines for security reports #9659

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
db8dee5
Additional guidelines for security reports
wiredfool Jun 5, 2026
ce62c52
Apply suggestion from @radarhere
aclark4life Jun 5, 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
14 changes: 14 additions & 0 deletions docs/handbook/security.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,3 +257,17 @@ If you cannot use GitHub, use the `Tidelift security contact
disclosure.

**Do not report sensitive vulnerability information in public.**

Additionally:

1. Please ensure that your issue is reproducable in **main**. We only
support the latest version. The one exception -- if your issue is
exploitable in the latest public release, but not in main, and the
pull request does not mention a security implication this may be an
unknown security issue that was inadvertely fixed.
2. Demonstrating a memory overflow is enough. Please do not weaponize
the reproducer to do remote code execution.
3. Please do not report unexpected Python exceptions as a DoS or a
memory safety bug. An issue that raises a Python exception in a
library is unlikely to be considered a security issue. This may or
may not be an ordinary bug depending on the context.