| 1 |
# Security Policy |
| 2 |
|
| 3 |
## Supported Versions |
| 4 |
|
| 5 |
There are no security-specific releases of calibre. Security bugs are fixed |
| 6 |
and released just like all other bugs. |
| 7 |
|
| 8 |
## Reporting a vulnerability |
| 9 |
|
| 10 |
To report security vulnerabilities, open a normal bug report in the |
| 11 |
[calibre bug tracker](https://calibre-ebook.com/bugs) and mark it private. |
| 12 |
|
| 13 |
Additionally, you can use GitHub Private security advisories against this |
| 14 |
repository to report issues. |
| 15 |
|
| 16 |
Note that I will generally respond to security communication within 72 hours. Once |
| 17 |
the bug is confirmed, it will be fixed or at least mitigated within another 72 |
| 18 |
hours, at which time the fix will typically be committed to master and hence be |
| 19 |
public. That timeline might be extended based on the severity of the issue and the |
| 20 |
current state of master in terms of making a new release. If so, it will be |
| 21 |
done in consultation with the issue reporter. |