Halo currently supports the versions listed below, where as:
- ✅ indicates an active development roadmap, is therefore maintaining, and will receive Security Vulnerability Report.
- ❌ indicates such version has already deprecated and will not be receiving Security Vulnerability Report.
| Version | Supported |
|---|---|
| 0.x | ❌ |
| 1.x | ❌ |
| 2.x | ✅ |
We first appreciate and are very thankful that you've found a vulnerability issue in Halo! By disclosing such issue to Halo development team you are helping Halo to become a much more safer project than before! ;)
To protect the existing users of Halo, we kindly ask you to not disclose the vulnerability to anyone except the Halo development team before a fix has been rolled out.
To report a vulnerability, please use GitHub private vulnerability reporting. This allows you to share the details privately with the Halo development team, and we will work with you on a fix and coordinated disclosure. The report form will ask for the affected versions, deployment method, environment details, reproduction steps, and impact.
If you are unable to use GitHub private vulnerability reporting, you can instead send the same information by email to
hi@halo.run.
- We will acknowledge your report within 5 business days.
- We will investigate the issue and keep you informed of our progress.
- We aim to release a fix within 90 days. We will coordinate the disclosure date with you, and credit you in the security advisory and release notes unless you prefer to remain anonymous.
This policy covers vulnerabilities in the Halo core repository. The following are generally out of scope:
- Issues that require an already-compromised administrator account, or existing access to the server or database.
- Vulnerabilities in third-party plugins, themes, or dependencies that do not have a demonstrated impact on Halo. Please report those to their respective maintainers.
- Reports for unsupported versions (0.x and 1.x).
- Reports from automated scanners without a working proof of concept.