Swift.org security

Security Process

For the protection of our community, Swift.org doesn’t disclose, discuss, or confirm security issues until our investigation is complete and any necessary updates are generally available.

Recent security updates are listed in the Security Updates section below.

Swift.org security documents reference vulnerabilities by CVE-ID when possible.

Reporting a security or privacy vulnerability

If you believe you have discovered a security or privacy vulnerability in a Swift.org project, please report it to us. We welcome reports from everyone, including security researchers, developers, and users.

To report a security or privacy vulnerability, please send an email to [email protected] that includes:

Please use Swift.org’s CVE PGP key to encrypt sensitive information that you send by email.

You’ll receive an email reply from Swift.org to acknowledge that we received your report, and we’ll contact you if we need more information.

How Swift.org handles these reports

For the protection of our community, Swift.org doesn’t disclose, discuss, or confirm security issues until our investigation is complete and any necessary updates are generally available.

Swift.org uses security advisories and our security-announce mailing list to publish information about security fixes in our projects and to publicly credit people or organizations that have reported security issues to us.

Security Updates