Legend:

• ✅ Currently supported, receives all security and other updates
• 🔙 Legacy support, receives backported security updates only
• ❌ Unsupported

The Vapor Core Team ask that known and suspected vulnerabilities be privately and responsibly disclosed by filling out a vulnerability report on Github¹. Vulnerabilities may also be privately and responsibly disclosed by emailing all pertinent information to security@vapor.codes.

⚠️ Please do not file a public issue! ⚠️

• You think you have discovered a potential security vulnerability in a Vapor package.
• You are unsure how a vulnerability affects a Vapor package.

• A member of the team will acknowledge receipt of the report within 3 working days. This may include a request for additional information about reproducing the vulnerability.
• We will privately inform the Swift Server Work Group (SSWG) of the vulnerability within 10 days of the report as per their security guidelines.
• Once we have identified a fix we may ask you to validate it. We aim to do this within 30 days. In some cases this may not be possible, for example when the vulnerability exists at the protocol level and the industry must coordinate on the disclosure process.
• If a CVE number is required, one will be requested through the GitHub security advisory process, providing you with full credit for the discovery.
• We will decide on a planned release date and let you know when it is.
• Prior to release, we will inform major dependents that a security-related patch is impending.
• Once the fix has been released we will publish a security advisory on GitHub and in the Server → Security Updates category on the Swift forums.