Thank you for sharing your experiences with us. Please follow the best practices below when making your submissions. The fastest way to get your bug fixed is to submit a patch, but we’ll do our best to help!
To privately report a potential vulnerability in WebM Project code, choose the Security template when creating the bug in our issue tracker. This will apply the Restrict-View-Security label to your issue, and it will remain private until reviewed.
The button below automatically populates a security-related issue in the tracker.
Before filing a new bug report, search the existing WebM issues (or WebP issues) database to make sure that your issue has not already been reported.
Tip! The search function defaults to searching only open issues. Consider changing the scope of your search to All issues.
If your issue has already been reported but you have a variation or new information to add, you can click “Add a comment below” on the left side of the issue screen to update the bug report.
A bug should be understandable years later by someone who will never talk to the reporter or assignee.
Be concise, but also make sure you have included all relevant information. Don’t assume the reader will have any context for what you are describing.
Enter a quick description of the problem, followed by the steps to reproduce it.
Define any acronyms or potentially unfamiliar terms you use.
