If you believe that you have discovered a security or privacy vulnerability in this open source project, please report it using the GitHub private vulnerability feature. Reports should include specific product and software version(s) that you believe are affected; a technical description of the behavior that you observed and the behavior that you expected; the steps required to reproduce the issue; and a proof of concept or exploit.
The project team will do their best to acknowledge receiving all security reports within 7 days of submission. This initial acknowledgment is neither acceptance nor rejection of your report. The project team may come back to you with further questions or invite you to collaborate while working through the details of your report.
Keep these additional guidelines in mind when submitting your report:
- Reports concerning known, publicly disclosed CVEs can be submitted as normal issues to this project.
- Output from automated security scans or fuzzers MUST include additional context demonstrating the vulnerability with a proof of concept or working exploit.
- Application crashes due to malformed inputs are typically not treated as security vulnerabilities, unless they are shown to also impact other processes on the system.
Do not include credentials, registry tokens, certificates, SSH keys, API keys, personal data, private registry names, or proprietary Compose files in reports, tests, examples, logs, or screenshots.
This project is independent of Apple and is not eligible for Apple Security Bounties.