⚠️ Please do not file public GitHub issues for security vulnerabilities as they are open for everyone to see! ⚠️
We encourage responsible disclosure practices for security vulnerabilities.
If you believe you've found a security-related bug, fill out a new vulnerability report via GitHub directly. To do so, follow these instructions:
Alternatively, drop an email to our CherryPy security mailbox instead of filing a ticket or posting to any public groups. It is currently set up to forward every incoming letter to both Jason R. Coombs and Sviatoslav Sydorenko. You can choose to email us directly. We will try to assess the problem in timely manner and disclose it in a responsible way.
If you prefer to, you may also report a security vulnerability through the Tidelift security contact. Tidelift will coordinate the fix and disclosure. This is not the maintainers' first preference, though. Please, use the GitHub's vulnerability reporting option, whenever possible.