| 1 | # Security Policy |
| 2 | |
| 3 | The IPFS protocol and its implementations are still in heavy development. This |
| 4 | means that there may be problems in our protocols, or there may be mistakes in |
| 5 | our implementations. We take security |
| 6 | vulnerabilities very seriously. If you discover a security issue, please bring |
| 7 | it to our attention right away! |
| 8 | |
| 9 | ## Reporting a Vulnerability |
| 10 | |
| 11 | If you find a vulnerability that may affect live deployments -- for example, by |
| 12 | exposing a remote execution exploit -- please **send your report privately** to |
| 13 | security@ipfs.io. Please **DO NOT file a public issue**. |
| 14 | |
| 15 | If the issue is a protocol weakness that cannot be immediately exploited or |
| 16 | something not yet deployed, just discuss it openly. |
| 17 | |
| 18 | ## Reporting a non security bug |
| 19 | |
| 20 | For non-security bugs, please simply file a GitHub [issue](https://github.com/ipfs/go-ipfs/issues/new/choose). |